On Thursday, October 24, 2002, at 02:16 AM, Warly wrote: [...]
As a consequence I propose one of the following solution:I say the second one... but make the unsupported dirs urpmiable also then. We need to leverage urpmi wherever we can. It would also, clearly, make sense to me that these are specifically labelled as unsupported (thus no updates/ subdir). No advisories will go out (from me) regarding them.
- either to create a sub dir call updates in the unsupported directory, that
will contains the updates made by contributors or mandrakiens for security
fixeson unsupported packges.
- or to let them directly access to the unsupported subdir, which is more or
less already a kind of unsupported updates directory (the only thing is that
it can contains several version of the the same package compiled with
different options, that is why I propose the first solution).
If folks want to post something to [EMAIL PROTECTED] or [EMAIL PROTECTED] with their "homebrewn" advisory regarding these unsupported updates, that is fine.
--
MandrakeSoft Security; http://www.mandrakesecure.net/
"lynx - source http://linsec.ca/vdanen.asc | gpg --import"
{FE6F2AFD: 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD}
PGP.sig
Description: PGP signature
