Gentoo Archives: gentoo-user

From: Alan McKinnon <alan.mckinnon@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] baselayout2/openrc question
Date: Tue, 02 Feb 2010 22:01:56
Message-Id: 201002022359.27523.alan.mckinnon@gmail.com
In Reply to: Re: [gentoo-user] baselayout2/openrc question by Mike Edenfield
1 On Tuesday 02 February 2010 23:40:17 Mike Edenfield wrote:
2 > On 2/2/2010 3:48 PM, Alan McKinnon wrote:
3 > > No, you completely misunderstand what stable, unstable and masked mean.
4 > >
5 > > You are using stable (and call it unstable which is wrong). What you call
6 > > masked is actually called unstable. Masked is something else entirely.
7 > >
8 > > Do not confuse these terms. They have *exact* meaning.
9 >
10 > Has there ever been any discussion on coming up with more precise
11 > wording for portage's error messages? I suspect a lot of confusion
12 > between masked/keyworded comes from the fact that portage calls them all
13 > "Masked", e.g.:
14 >
15 > !!! All ebuilds that could satisfy "=app-editors/vim-7.2.303" have been
16 > masked.
17 > !!! One of the following masked packages is required to complete your
18 > request:
19 > - app-editors/vim-7.2.303 (masked by: ~amd64 keyword)
20 >
21 > Not that I came up with any better wording off the top of my head, but
22 > is the portage team open to suggestions? Or has this issue been beaten
23 > to death already?
24
25
26 "mask" is a computer term. It means something that defines an exclusion list.
27 All packages in gentoo have masks, even if they are null. "Stable" can be
28 considered to be a mask, it just happens to be empty so is always available on
29 a system where the arch matches.
30
31 When the devs talk about "hard masking" they mean something with an entry in
32 packages.mask. Other terms are completely understood: arch, ~arch, etc.
33
34 When users miscomprehend the terminology, it's not a failure in the
35 terminology it's a failure by the user. Human languages are like that. No
36 matter how well you try and nail down a definition for all time, users of the
37 language will always try to change stuff.
38
39 The current terms work well. Changing them is unlikely to be well received as
40 they are so deeply entrenched already.
41 --
42 alan dot mckinnon at gmail dot com