On 1/9/08, Ciaran McCreesh <[EMAIL PROTECTED]> wrote: > On Wed, 09 Jan 2008 17:49:40 +0100 > "Wulf C. Krueger" <[EMAIL PROTECTED]> wrote: > > >> What's the proper fix for when keyword requests stagnate in > > >> bugzilla? > > > That depends upon whether the keyword request is important. > > > > Let's take a real world example: KDE 3.5.5 is old, buggy and has > > some important issues which won't be fixed anymore. > > Yet it's the most proven version on mips. > > > > If it is (and legitimately so > > > > I hope you'll accept it when I say that 3.5.5 is such a legitimate > > case now. > > Why? It was good enough to be keyworded stable at one point. > > > What would you suggest to do now? I think we've done all we could > > short of the following: > > > > a) Drop all keywords but those of mips. Leaves mips and, more > > importantly, its users with a vulnerable and unmaintained set of > > packages. > > ...and break the tree spectacularly, causing huge amounts of pain for > your fellow developers when they encounter horrible repoman output when > they try to do anything. > > > b) package.mask 3.5.5 with a big, fat warning and let the users > > decide. Same drawbacks as a). > > ...and break the tree spectacularly, causing huge amounts of pain for > your fellow developers when they encounter horrible repoman output when > they try to do anything. > > > c) Drop 3.5.5 from the tree. The cleanest but most radical solution. > > If mips' users want KDE, they would have to bug (sic!) the mips team. > > ...and break the tree spectacularly, causing huge amounts of pain for > your fellow developers when they encounter horrible repoman output when > they try to do anything.
Actually if they dump kde-3.5.5 and anything depending on it, then they don't break the tree and everyone is happy, no? -- gentoo-dev@lists.gentoo.org mailing list
