On Sunday 26 February 2006 18:15, Bo Andresen <[EMAIL PROTECTED]> wrote about 'Re: [gentoo-user] What happens with masked packages?': > On Sunday 26 February 2006 21:40, Boyd Stephen Smith Jr. wrote: > > > How exactly is is you want this to work. > > > > My proposal at this point, would be for an additional restriction on > > packages based on a new UPSTREAM variable in the ebuild itself, > > ACCEPT_UPSTREAM variable in make.conf / the environment, and the > > package.upstream file in /etc/portage. > > I read your previous posts about this as that you wanted it to be easier > to get beta versions but what you want is in fact the exact opposite - > further restriction. Now I get it.
Well, it would make it easier by moving them /out/ of package.mask and putting them in a classification similar to KEYWORDS. Then, to get all the betas my heart desires I can simply set ACCEPT_UPSTREAM="BETA", instead of manually pawing through package.mask to add them all to package.unmask. In particular, I update my system regularly with emerge -avtuND world. This won't give me any notification that betas are available but masked. I'd like to configure my system so that any new betas of kaffeine, kmplayer, ktorrent, and the nsplugins for kaffeine and kmplayer would be installed with having to regularly check on them myself. I'm imaging the default provided by the base profile would be ACCEPT_UPSTREAM="RELEASE BUG_FIX SECURITY_FIX" so that packages with UPSTREAM="BETA" (or HEAD, SNAPSHOT, ALPHA, PRE_RELEASE, RELEASE_CANDIDATE, alia al) would not be installed. (Until you changes your ACCEPT_UPSTREAM in make.conf or edit /etc/portage/package.upstream) I'd like upstream stability more cleanly separated from ebuild stability. Ciaran did clarify the roles of the various keywords and the global and profile-provided package.masks; from my experience I couldn't see the degree of separation that is intended -- dismissing the few abuses that are still in the portage tree. I still think my system would be better, but I'm biased. :) -- "If there's one thing we've established over the years, it's that the vast majority of our users don't have the slightest clue what's best for them in terms of package stability." -- Gentoo Developer Ciaran McCreesh -- gentoo-user@gentoo.org mailing list
