On Wed, Apr 2, 2014 at 4:23 PM, Alex Xu <alex_y...@yahoo.ca> wrote: > On 02/04/14 04:02 PM, Rich Freeman wrote: >> Another option might be to have a tag in metadata.xml that flags >> packages as never-stable > > Arguments have been made that such packages do not belong in g-x86. >
Why not? In general I think packages should be stabilized whenever possible, but there are situations where it just doesn't make sense. One situation I've run into is something like a game that has an open-source client and a proprietary server. If the server is updated in conjunction with a same-day client update then all past versions are instantly broken, and it is appropriate for users to immediately use the new client. There is no value at all in a testing/stable lifecycle for such a package, so it stays in ~arch. If a package is flagged as never-stable inappropriately by all means complain to QA/whatever. Rich
