portage flags - nothing new... but worth to mention...

Xor · Tux's lil' helper Joined: 07 Jul 2002 Posts: 144

Proposal for Extended emerge flags

U = Unstable
S = Security

so folks now if a certain package is important (Security) or if they use ~arch if it is a regular (released) or unstable package

Maybe thoses flags should only be displayed on request ( --pkg-ext-info or make.conf) as it will certainly break scripts

phong · Posted: Tue Nov 05, 2002 4:01 pm Post subject:

This is more of a discussion thread than a support thread - moving to Gentoo Chat.
_________________
"An empty head is not really empty; it is stuffed with rubbish. Hence the difficulty of forcing anything into an empty head."
-- Eric Hoffer

Proteus · Posted: Tue Nov 05, 2002 4:24 pm Post subject:

Cannot see a reason for this.
Maybe I did not understand exactly what you wanted to tell...
Can you explain with more detail?
_________________
Greetings,
Proteus

mksoft · l33t Joined: 28 May 2002 Posts: 844

The security flag should be important 'cause if the security updated ebuild is not part of "system" or not in the world file, it won't be updated, and one can miss the security announcment.

Question is how ebuilds can be flagged for security update :?:

AFAIK there's no such mechanism in place right now.

Maybe another branch (as in folder) for security updates, which takes precedence over the regular tree and is taken into account by emerge :?:

For the unstable flag, it is not very important since it can be overridden easily with env var of:

rac · Posted: Tue Nov 05, 2002 11:31 pm Post subject:

mksoft · l33t Joined: 28 May 2002 Posts: 844

IIRC, unstable package won't even appear in the output of emerge -s _package_name, while masked one will appear with masked status (please correct me if wrong).

So right now comparing the output of: