Holly Bostick wrote:
The thing is Portage doesn't *remember* ACCEPT_KEYWORDS, beyond the
original compile in which it is used. So if you use it, and keep the
package, as soon as you do an emerge -u world, Portage will try to
downgrade the package to the last stable version, which is the
Steve [Gentoo] wrote:
The only way in which I'm not yet as convinced as you are is with
respect to dependencies. I'm comfortable with the idea that I browse
the bugs to verify that none of the issues affect my install directly -
then to accept an unstable version of a specific package...
I'd have thought lots of people in the gentoo crowd would have been
eagerly awaiting subversion 1.2.x with its substantial new reserved
checkout - but nothing seems to have moved forward.
Portage (by default) still gives me version 1.1.3... but version 1.2 has
been available for a couple of
Steve [Gentoo] wrote:
I'd have thought lots of people in the gentoo crowd would have been
eagerly awaiting subversion 1.2.x with its substantial new reserved
checkout - but nothing seems to have moved forward.
Portage (by default) still gives me version 1.1.3... but version 1.2
has been
Steve [Gentoo] wrote:
I'd have thought lots of people in the gentoo crowd would have been
eagerly awaiting subversion 1.2.x with its substantial new reserved
checkout - but nothing seems to have moved forward.
you must have missed this link from the gentoo homepage (on the left):
Marco Matthies wrote:
Gentoo leaves packages in unstable for a default period of time to make sure
they work allright. If you want the newest version of a package, you must tell
portage to do so by putting the appropriate stuff (subversion and it's
dependencies) in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve [Gentoo] wrote:
Hmmm - that all sounds sane, but what is this default period of time?
What criteria must be met in order for a masked package (and
specifically for Subversion) to become unmasked?
At least a month and there can't be any
Steve [Gentoo] wrote:
Hmmm - that all sounds sane, but what is this default period of time?
What criteria must be met in order for a masked package (and
specifically for Subversion) to become unmasked?
I *think* it is something along the lines of 30 days without a bug,
not 100% sure though.
8 matches
Mail list logo
