From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1FDP6t-0003US-Lx for garchives@archives.gentoo.org; Sun, 26 Feb 2006 16:51:04 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k1QGo74q029983; Sun, 26 Feb 2006 16:50:07 GMT Received: from pb78.olsztyn.sdi.tpnet.pl. (pb78.olsztyn.sdi.tpnet.pl [213.76.235.78]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k1QGfV0B032645 for ; Sun, 26 Feb 2006 16:41:31 GMT Received: (qmail 14546 invoked by uid 1000); 26 Feb 2006 17:34:31 +0100 Date: Sun, 26 Feb 2006 17:34:31 +0100 From: Mariusz =?iso-8859-2?Q?P=EAkala?= To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] What happens with masked packages? Message-ID: <20060226163431.GA9015@cthulhu.sdi.tpnet.pl> Mail-Followup-To: gentoo-user@lists.gentoo.org References: <200602222055.42113.tcoulon@decoulon.ch> <200602251334.28098.bss03@volumehost.com> <20060225234745.GC10446@cthulhu.sdi.tpnet.pl> <200602252316.36269.bss03@volumehost.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="n8g4imXOkfNTN/H1" Content-Disposition: inline In-Reply-To: <200602252316.36269.bss03@volumehost.net> User-Agent: Mutt/1.5.11 X-Archives-Salt: dd72e8b0-7a04-44ea-9597-836c98ad3351 X-Archives-Hash: c99f5e56a8ba2769eb12a134a75b232d --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2006-02-25 23:16:36 -0600 (Sat, Feb), Boyd Stephen Smith Jr. wrote: > > > So, it's based on the collective opinion of the gentoo developers? > > > Wouldn't it be better to put that in the hands of the gentoo user? > > > > IMHO it already is. It's called PORTAGE_OVERLAY. >=20 > Again, hard to do automatically. Wheras, if I could just set=20 > ACCEPT_UPSTREAM=3D"BETA" I'd get all the betas. Or I could use=20 > package.upstream and but in "kde-extra/kaffeine ALPHA" and get anything= =20 > assigned more than a snapshot number for that package. (Instead of=20 > manually checking after each sync to see if there's a new, masked=20 > version.) In 'man 5 ebuild' I see: Atom Versions It is nice to be more specific and say that only certain versions of= atoms are acceptable. Note that versions must be combined with a prefix (see= below). Hence you may add a version number as a postfix to the base: sys-apps/sed-4.0.5 sys-libs/zlib-1.1.4-r1 net-misc/dhcp-3.0_p2 Versions are normally made up of two or three numbers separated by per= iods, such as 1.2 or 4.5.2. This string may be followed by a character such = as 1.2a or 4.5.2z. Note that this letter is not meant to indicate alpha, = beta, etc... status. For that, use the optional suffix; either _alpha, _be= ta, _pre (pre-release), _rc (release candidate), or _p (patch). This means for = the 3rd pre-release of a package, you would use something like 1.2_pre3. I suppose that you could prepare a script that builds your /etc/portage files to unmask packages with _beta versions, or with any other criteria contained in ebuild. --=20 No virus found in this outgoing message. Checked by "grep -i virus $MESSAGE" Trust me. --n8g4imXOkfNTN/H1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (GNU/Linux) iD8DBQFEAdiXIzblgXdKMIURAiouAKCgQxuUR+yfA19cijoc4wM96zeAJQCggHpJ b5GUvo2ESDu0a4C80yWiz2o= =ji+N -----END PGP SIGNATURE----- --n8g4imXOkfNTN/H1-- -- gentoo-user@gentoo.org mailing list