public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Steve [Gentoo]" <gentoo_steve@shic.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Subversion 1.2
Date: Thu, 14 Jul 2005 20:48:00 +0100	[thread overview]
Message-ID: <42D6C170.6090402@shic.co.uk> (raw)
In-Reply-To: <42D6B054.7050606@saunalahti.fi>

Petteri Räty wrote:

>>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 major bugs reported to
>bugs.gentoo.org. About specifics on Subversion you need to ask its
>maintainer. It will stay masked as long as needed for the maintainer to become sure that the package really is stable.
>  
>
Hmmm... I suppose that suggests there were some major bugs...  using 
bugs.gentoo.org is new to me - it seems that's where I was missing a 
pointer.  Thanks again.  I didn't want to pester the maintainer with 
superfluous questions as to why packages are masked. It seems a pity 
that all the information isn't available on one page... using 
packages.gentoo.org and bugs.gentoo.org together gives the right info - 
even if it requires a little bit more effort. :-)  I'll be sure to see 
if I can offer feedback to the bugzilla database if I find something 
relevant to add.

>>Ideally I'd like to follow the natural upgrade cycle in future. 
>>Wouldn't putting those lines in my package.keywords file prevent me getting, say, version 1.3 automatically when I do an "emerge -uD world" in another few months?
>>    
>>
>No it would not. You are just changing the accepted the keywords for
>Subversion. Portage always chooses the latest version with accepted
>keywords. If just add dev-util/subversion you say that you will accept
>every version marked as ~x86 or you can use =dev-util/subversion-1.2.1
>to only mark one version. If you don't use version numbers, you will
>always update to the latest version. If you lock down the version
>number, the next time you will update if after there is a version
>greater then 1.2.1, which is marked stable (x86).
>  
>
Ah, ha.  That sounds sensible - now I follow.  My USE confusion is 
probably that I'd referred to some wrong/out-of-date documentation... 
when I use ACCEPT_KEYWORDS in place of USE it now behaves just how I had 
previously expected it should have done.

# ACCEPT_KEYWORDS="~x86" emerge -uD subversion

This does what I'd originally intended to try...  (and doesn't force me 
to remember how to spell the  dependencies.) I assume there's no 
significant advantage I've missed in preferring to use the 
package.keywords file instead?

>Hopefully I answered this.
>  
>
I think you did... Thanks!


-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-07-14 19:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14 15:32 [gentoo-user] Subversion 1.2 Steve [Gentoo]
2005-07-14 17:02 ` Kurt Guenther
2005-07-14 17:26 ` Marco Matthies
2005-07-14 18:20   ` Steve [Gentoo]
2005-07-14 18:35     ` Petteri Räty
2005-07-14 19:48       ` Steve [Gentoo] [this message]
2005-07-14 20:58         ` Holly Bostick
2005-07-15 14:55           ` Steve [Gentoo]
2005-07-15 15:18             ` Zac Medico
2005-07-14 23:12     ` Marco Matthies

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42D6C170.6090402@shic.co.uk \
    --to=gentoo_steve@shic.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox