public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marco Matthies <marco-ml@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Subversion 1.2
Date: Fri, 15 Jul 2005 01:12:04 +0200	[thread overview]
Message-ID: <42D6F144.1030103@gmx.net> (raw)
In-Reply-To: <42D6ACFB.3010507@shic.co.uk>

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.

>> Here, i just did it myself by putting this in my package.keywords
>> (create this file if it doesn't exist) :
>>
>> =dev-util/subversion-1.2.1              ~x86
>> =dev-libs/apr-util-0.9.5                ~x86
>> =dev-libs/apr-0.9.5                     ~x86
>>  
>>
> In one way this looks better than my fiddling with USE - however I'm
> reluctant to choose specific versions in a durable configuration file. 
> 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?

the line:
=dev-util/subversion-1.2.1              ~x86
means that you tell portage that you'll accept subversion, version 1.2.1
exactly, with a keyword of '~x86'. You can use '>=' instead of '=',
which means any version equal or greater than 1.2.1.
the two following lines were the two dependencies i found by trying
'emerge -uD subversion'.

once 1.3 or any version higher than 1.2.1 becomes stable (marked 'x86'),
it will be considered by portage as well and will be merged.

Hope that helps,

Marco
-- 
gentoo-user@gentoo.org mailing list



      parent reply	other threads:[~2005-07-14 23:15 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]
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 [this message]

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=42D6F144.1030103@gmx.net \
    --to=marco-ml@gmx.net \
    --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