On Tue, 31 Oct 2006 17:57:06 +0100 Jakub Moc <[EMAIL PROTECTED]> wrote: | > How exactly does this affect package maintainers, apart from the | > cosmetic problems of having an old ebuild lying around? As far as I | > can see, it doesn't affect the maintenance burden, | | Of course it does... Lots of people can't remove outdated broken cruft | because $ebuild still depends on something since $arch has been | slacking for months. Lots of people are forced to maintain outdated | junk in this way, it's not like it's just sitting there doing nothing.
Uh, dude... If people are maintaining out of date packages, they're doing something wrong. Old packages, by and large, should *not* be modified. | So again, if some arch can't be bothered to answer keywording bugs for | months, no point in complaining that the maintainer finally gets | pissed off enough to just punt the last ebuild keyworded for that | arch. Simply leaving those ebuilds alone takes no effort. -- Ciaran McCreesh Mail : ciaranm at ciaranm.org Web : http://ciaranm.org/ as-needed is broken : http://ciaranm.org/show_post.pl?post_id=13
signature.asc
Description: PGP signature
