Please do not delete my svn:externals for no reason without asking me. The packager ignores svn:externals, so there is no reason for you to unilaterally change my repository setup. I don't keep standalone copies of libraries laying around in my AddOns folder. I use svn:externals for a reason.
If you are changing the packager so that it cannot handle a repository with both a .pkgmeta file present and svn:externals set, or are implementing some rule against using svn:externals on Curse repositories, please make an announcement on the front page, or send out PMs to authors, so I can move my repository elsewhere.
I use svn:externals to get the libraries into my local copy, and keep those copies updated, with a minimum of effort. It has nothing to do with the packager. If you know of some less "decidedly suboptimal" way to keep local copies of libraries in a working copy up to date, without cluttering up my addons folder with a bunch of crap, I'm all ears (or eyes, as the case may be).
Yes, but then I have a bunch of crap cluttering up my addons folder, which I specifically stated (twice) that I do not want, and there's absolutely no reason I should have to do that, when using svn:externals is (a) more convenient for me, (b) does not affect the packaging of my addon in any way, and (c) has absolutely no effect on anyone else at all.
If you, personally, don't like using svn:externals, don't use it, but frankly I'm pretty annoyed that other people think it's okay to go screwing with other people's repositories to match their personal perferences. It'd be like me going into someone else's addon and reformatting their code to use tabs instead of spaces, just because I, personally, don't like using spaces for indentation, except worse because they're not going to log into the game and get spammed with errors because I actually broke their working copy as an addon.
Well, then I apologise. And no I did not change anything because "I'm an admin". I changed it because it's an open repository and I couldn't believe for the life of me that anyone actually wanted svn:externals kept around since it slows down svn updates hugely. Especially if you have many addons checked out (like I do).
FWIW, I make use of svn:externals in the same way and for (I think) the same reasons as Phanx.
If someone has synched one of my repositories and disabled all other addons but that project, it should load and run correctly. If it doesn't, then I would feel like my project wasn't properly configured. Using svn:externals seems like the best way to accomplish that.
If someone uses a repository version of my projects, i expect them to know wtf they are doing, or stick to the zips. :P
Its not the only thing that stops working, localizations are not present in checkouts, some code may be enabled thats usually supposed to be commented out by packager tags (debug things), etc.
The stand-alone zips don't bother me, and considering my addon directory consists of 95% repository checkouts, i personally dislike any addon that forces an extra copy of libs down my throat with svn:externals, luckily i don't think i use any.