-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/27/07 22:17, [EMAIL PROTECTED] wrote: >> That is, all software that makes it to into testing should be >> stable and release quality and ready for testing with *the rest of the >> packages slated for the next release*. > > Ok. In the event of a piece of software which is likely to need little > testing and be updated upstream several times between releases (such as > Opera) how would this best be handled? Should one wait until a few month > prior to the next release instead of repackaging it and sending it back > through the various releases multiple times between Debian releases.
No. There's no harm in sending multiple versions thru the cycle. If there are no other "blockages" or problems, a package is supposed to sit in Unstable before being automagically moved to Testing. In the case of Opera, since Debian can't distribute it, what would be packaged would probably be an "installer" script that would grab the DEB or tarball from opera.com and then install it onto the system. - -- Ron Johnson, Jr. Jefferson LA USA Give a man a fish, and he eats for a day. Hit him with a fish, and he goes away for good! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG05aOS9HxQb37XmcRAmixAKDtkvP1MFiy9w2WS1lGweAbrgykAQCeOmX8 I2a+70K1clE36JvQZwSftu0= =MjHi -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
