Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 41099 - wildcard package.mask/unmask matching
Summary: wildcard package.mask/unmask matching
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High enhancement
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-10 04:30 UTC by Mike Williams
Modified: 2004-02-12 07:07 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Williams 2004-02-10 04:30:42 UTC
With the fast development of the 2.6 kernel, and living on the unstable edge, I am (and many many other people are) being bombarded with a new version every few days. That's a lot of bandwidth, and space for kernels I'm not going to use.
What I'd like to see is wildcard matching in package.mask (and package.unmask) allowing me to mask all development-sources-2.6.?_rc?, etc, etc.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 Marius Mauch (RETIRED) gentoo-dev 2004-02-11 10:12:05 UTC
what's wrong with masking sys-kernel/development-sources completely ?
Comment 2 Marius Mauch (RETIRED) gentoo-dev 2004-02-11 10:33:48 UTC
ignore that, I misread your comment.
I don't think that adding wildcards to these files is a good idea as it will likely break other things as well. A workaround is to exclude the things you don't want in RSYNC_EXCLUDEFROM (see `man make.conf`) which supports wildcards.
Comment 3 Nicholas Jones (RETIRED) gentoo-dev 2004-02-11 17:55:09 UTC
I don't follow what you want.

What's wrong with the masks as they are?
Read the docs and use a depend atom...

I'm also not fond of the idea of a wildcard and probably won't
ever support such a thing as it _WILL_ become a nightmare for
devs to figure out why userL exploded in an email flame war.

Comment 4 SpanKY gentoo-dev 2004-02-11 18:04:00 UTC
i'd agree with nick on this one ... masking is just fine as it is ...

if you dont want to follow such a constantly updated kernel then dont use it and/or just inject the new ones as you go

personally i build a new 2.6 almost everyday :P
Comment 5 Mike Williams 2004-02-12 01:52:06 UTC
Fair enough, you're right.
I did find a 'nice enough' answer, mask all development-sources, and unmask the ones I want.

Cheers
Comment 6 SpanKY gentoo-dev 2004-02-12 07:07:01 UTC
we still love you