>But since I greased your beard with so much honey: what I dislike is, that you have too many packages in your repos.

Well hey I've got so many systems to administer and use, I need all of it. And the only sane choice is to have everything in a single repo. It's just infeasible to add tons of .repo files to every system and keep them up to date (well yeah turns out you can use $releasever or some magic string in SUSE too, but that's a recent discovery). gcc-4.5 for example used to be in home:rguenther, then it moved to devel:gcc.

On the other hand, all packages that accumulated in my repo are just a sign of openSUSE lacking them. Of course I have been busy in SR'ing pieces, but then there are sometimes nitpicky situations (kernel-source; solvable) or unreasonably conservative/inertial gatekeepers (net-tools; BNC#492665, FATE#307200).

In a way, you could say that the amount of RPMs in my repo is a (combined) factor of and index about:

1. interesting stuff, new stuff
2. stuff that openSUSE can't include
3. different stuff (customization like shell prompts - something that is unlikely to ever make it upstream)
4. discontent with openSUSE

Maybe I should split my SRPM directory up into subdirectories based upon these categories to keep an easy count. Watch out for when directory number 4 grows.

>For a distribution, that's fine, but if you only look >for some special packages, it's awful to pull a lot of other stuff. That >depresses the popularity of your repos considerably in my eyes.

Well let me put in this disclaimer:

• If User does not like it, don't use it
• User is not required to download more than what the dependencies require
• User is not required to install more than what the dependencies require
• Dependencies are built in good faith, especially you won't get the much-needed net-tools fix forced into the system (unless you explicitly request to have a jeng-approved system by installing jeng-*-packages).