[Frugalware-devel] Packaging policy

[Russell Dickenson]

2008/3/18 Miklos Vajna <vmiklos at frugalware.org>:
> On Mon, Mar 17, 2008 at 08:06:21AM +1000, Russell Dickenson <russelldickenson at gmail.com> wrote:
>  > I'm sure I've raised this before but only in IRC IIRC ( :) ).  Does
>  > Frugalware have a packaging policy - e.g. stating what's in and what's
>  > not?  With several new packagers, I've seen a few beta and alpha
>  > applications being packaged.  I can understand releases such as
>  > OpenOffice.org XX RC2 being packaged because the previous version
>  > wouldn't build on the 64-bit platform.
>  >
>
>  i agree and i think that's the current situation as well.

In taking a brief look at some of the newly packaged applications it
seems that there are a few beta applications in the current
repository.  "gimmie" is just one example.  Should beta/rc/pre-release
applications perhaps be removed from the repositories completely or
simply moved into a new repository?

I see that there's some benefit to packaging beta/rc/pre-release
applications, providing it's quick clear and obvious that the version
packaged is not the final release.  For Kalgan's release, a
pre-release/release candidate of OO.org had to be included as the
earlier version couldn't be compiled on 64-bit.  Firefox 3 is
currently in beta and it would be an advantage to have users testing
it now.

I don't have any easy answer to this situation as some may not see the
current situation being a problem.  For my purposes though, I don't
want to be downloading pre-release software from current.


May you always be Frugal,

Russell Dickenson (AKA phayz)