Gentoo Archives: gentoo-amd64

From: Mark Knecht <markknecht@×××××.com>
To: gentoo-amd64@l.g.o
Subject: [gentoo-amd64] ~amd64 vs portage.unmask
Date: Tue, 27 Jan 2009 22:48:59
Message-Id: 5bdc1c8b0901271448v2e8ca7ccj54dfb5d7c3d93763@mail.gmail.com
1 I seem to be a bit confused about the correct usage of ~amd64 vs
2 unmasking a package in the portage.unmask file. Thanks in advance.
3
4 Some time ago I was installing a piece of audio software that righted
5 a newer glib file. I got it installed using ~amd64 in the
6 package.keywords file. However over time, because that is there,
7 portage has built newer versions of glib which I didn't really need. I
8 try to run this machine pretty much stable and only deviate when I
9 have a specific need to.
10
11 As I was looking at files this afternoon I wanted to remove from keywords
12
13 dev-libs/glib ~amd64
14
15 and add to package.unmask
16
17 =dev-libs/glib-2.18.4
18
19 with the intention of waiting until that became stable at which time
20 eix-test-obsolete would tell me that the falgs are not necessary, but
21 when I do that portage trys to downgrade glib to 2.16.5 which won't
22 work for me.
23
24 I then thought the right way to do this might actually to use both
25
26 dev-libs/glib ~amd64
27
28 and
29
30 <=dev-libs/glib-2.18.4
31
32 I tried this changing 2.18.4 to 2.18.3 expecting to see it want to
33 downgrade to that version but it didn't.
34
35 What's the proper way for me to limit glib at the currently installed
36 revision level?
37
38 Thanks,
39 Mark

Replies

Subject Author
Re: [gentoo-amd64] ~amd64 vs portage.unmask Sebastian Redl <sebastian.redl@×××××××××××.at>