From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Lgkyx-00070k-Qr for garchives@archives.gentoo.org; Mon, 09 Mar 2009 19:17:48 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A1F9DE04BC; Mon, 9 Mar 2009 19:17:06 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 58262E04BC for ; Mon, 9 Mar 2009 19:17:06 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 09487642B8 for ; Mon, 9 Mar 2009 19:17:06 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: -3.589 X-Spam-Level: X-Spam-Status: No, score=-3.589 required=5.5 tests=[AWL=0.010, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dtXBwQMjb67G for ; Mon, 9 Mar 2009 19:16:59 +0000 (UTC) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id C2057646C6 for ; Mon, 9 Mar 2009 19:16:57 +0000 (UTC) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Lgky4-0006De-9a for gentoo-user@gentoo.org; Mon, 09 Mar 2009 19:16:52 +0000 Received: from pool-173-71-204-106.clppva.fios.verizon.net ([173.71.204.106]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 09 Mar 2009 19:16:52 +0000 Received: from en.ABCD by pool-173-71-204-106.clppva.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 09 Mar 2009 19:16:52 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: ABCD Subject: [gentoo-user] Re: @kde-4.2 Date: Mon, 09 Mar 2009 15:16:23 -0400 Message-ID: References: <20090309084015.1735cd5c@krikkit.digimed.co.uk> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pool-173-71-204-106.clppva.fios.verizon.net User-Agent: Thunderbird 2.0.0.19 (X11/20090106) In-Reply-To: X-Enigmail-Version: 0.95.7 Sender: news X-Archives-Salt: aa189257-bef6-4d9f-95de-776fe7a6a828 X-Archives-Hash: ac9291e3e41c556c4a76e47f64c58293 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 James wrote: > Neil Bothwick writes: >> cat /etc/portage/sets/kde4.3 >>/etc/portage/package.keywords >> Or make package.keywordsa directory and simply put a copy of the sets >> file in there (or a symlink to the sets file). This is the more >> manageable option. > > Interesting approach. I usually like to follow the gentoo recommended > practices. I get the feeling that "sets" via portage 2.2 is very > much a work in progress. So which of these approaches is likely > to become the de'facto method? > > Also, I omitted the "~amd64" at the end of all of those manual > entries into my package.keywords file. It work without them. > So my question is the "-amd64" entry on every line of my package.keywords > deprecated now with portage 2.2? > > > James > If you are using the kde-testing overlay, there are files that you can symlink under /etc/portage/package.{keywords,unmask}/ to unmask/keyword particular versions of KDE. Note also that "any file in [/etc/portage] that begins with 'package.' can be more than just a flat file. If it is a directory, then all the files in that directory will be sorted in ascending alphabetical order by file name and summed together as if it were a single file" (from portage(5)). To be precise, it can be an entire directory tree, and still work the same way. A line in package.keywords without any KEYWORDS implies "~${ARCH}" (again, see portage(5)). With the exception of sets and FEATURES=preserved-libs, everything in portage-2.2 is in portage-2.1.6.*, which is now stable just about everywhere, so this behavior is at least that old (although I believe it has been around longer). - -- ABCD -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkm1awcACgkQOypDUo0oQOpvhgCdEAKRJp1kSFoff++jTn+JQYvp VZ8An0/7OMDSrfddocWGkJFiArV4D8tZ =gruJ -----END PGP SIGNATURE-----