On Fri, 24 Feb 2006 14:57:43 -0600 "Boyd Stephen Smith Jr." <[EMAIL PROTECTED]> wrote: | > ~arch means a package is a candidate for going into arch after | > further testing, if said testing does not turn up new bugs. This | > means that both the ebuild *and* the package should be likely to be | > stable. | | So, betas shouldn't ever be ~arch? Or is your definition of stable | broad enough to include betas?
Entirely dependent on the upstream. I've had Vim beta releases in ~arch, for example, because I'm confident in upstream's ability to do beta releases without screwing up. | > -* means the package is in some way architecture or hardware | > independent (e.g. a binary only package), and so will only run on | > archs that are explicitly listed. | | So, I guess glibc-2.3.6-r3.ebuild is using -* incorrectly? Probably. | > Any package setting KEYWORDS="-*" and nothing else is abusing -*, | > and will flag a warning on the QA checkers. | | You mean like gcc-4.1.0_pre20060219.ebuild? Yyyyup. The -* abuse is one of the many things on QA's list of "stuff we want to get fixed". However, it's considered extremely low priority on existing packages. -- Ciaran McCreesh : Gentoo Developer (Wearer of the shiny hat) Mail : ciaranm at gentoo.org Web : http://dev.gentoo.org/~ciaranm
signature.asc
Description: PGP signature
