On Fri 2008-01-18 16:25 , Grigorios Bouzakis wrote:
On Fri, Jan 18, 2008 at 02:50:31PM +0100, bardo wrote:
[...]
As i had also stated in my previous illiterate mail (sorry for that), IMHO yes, TU's should upload to community only packages that have high demand by users. This is also the case now for developers about uploading packages in extra too. I think i am one of the few people who dont use community anymore and that fact is one of the main reasons. The community repo has gone very big, with many high demand packages staying in unsupported, while many of the packages in community have low usage, are old projects with almost no updates for years and build in a couple of secs.
One of the worst thing a TU can do is to move a high demanded package that he doesn't use in [community]. This way he can't test it properly, and no, just trying if it runs one time, before committing it in the repo is not "proper testing".
Even though the later isnt a reason for them to not be in community. If TU's want to upload to community packages they use before adding them to unsupported they should instead consider creating a custom local repo just like everyone else.
Just use common sense, IMVHO there is no problem if a TU moves 5 packages he uses on every machine in [community]. It *is* a problem if he moves 300 packages.
[...]
Cheers, -- Alessio Bolognino Please send personal email to themolok@gmail.com Public Key http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xFE0270FB GPG Key ID = 1024D / FE0270FB 2007-04-11 Key Fingerprint = 9AF8 9011 F271 450D 59CF 2D7D 96C9 8F2A FE02 70FB