| View previous topic :: View next topic |
| Author |
Message |
bluesky
Apprentice
Joined: 14 Aug 2002
Posts: 230
Location: USA
|
 Posted: Fri Jun 20, 2003 11:20 am Post subject: What makes and what breaks? |
 |
|
The package.mask helps to mask those packages that most likely to break the system, so it is a good thing. Does it means we should not touch it at all? Give a simeple example that we can modify it safely.
_________________
bluesky
"free as the wind" |
|
| Back to top |
|
 |
flurix
n00b
Joined: 24 Mar 2003
Posts: 26
|
| Posted: Fri Jun 20, 2003 1:18 pm Post subject: |
|
|
Still trying to hack, huh? 
If you really want to risk, find lines that match your particular package and comment them out. Beware that there are more than one place (file) where a package can be masked. Good luck. |
|
| Back to top |
|
|
Pythonhead
Developer
Joined: 16 Dec 2002
Posts: 1801
Location: Redondo Beach, Republic of Calif.
|
| Posted: Fri Jun 20, 2003 2:29 pm Post subject: |
|
|
Each package has a comment that explains why its being masked. So you can usually read that and decide yourself.
Most are there because they haven't been properly tested. |
|
| Back to top |
|
|
flurix
n00b
Joined: 24 Mar 2003
Posts: 26
|
| Posted: Fri Jun 20, 2003 5:53 pm Post subject: |
|
|
| Quote: | | Most are there because they haven't been properly tested. |
Interesting. I thought ~arch is the proper way of saying "it has not been tested, so
beware". And the portage mask is something like "don't use it as it won't compile,
install or work as expected (or not at all)".  |
|
| Back to top |
|
|
bsolar
Bodhisattva
Joined: 12 Jan 2003
Posts: 2764
|
| Posted: Fri Jun 20, 2003 6:13 pm Post subject: |
|
|
| flurix wrote: | Interesting. I thought ~arch is the proper way of saying "it has not been tested, so
beware". And the portage mask is something like "don't use it as it won't compile,
install or work as expected (or not at all)". |
My interpretation is, roughly: stable "has to work", ~arch "should work" and package.mask "might work, but..." (the comment as reference) or, in the worst case, "it doesnt work because..." (again see the comment).
Untested or not enough tested packages, if in the portage tree, should be masked in package.mask.
_________________
I may not agree with what you say, but I'll defend to the death your right to say it. |
|
| Back to top |
|
|
flurix
n00b
Joined: 24 Mar 2003
Posts: 26
|
| Posted: Fri Jun 20, 2003 6:22 pm Post subject: |
|
|
| Quote: | | My interpretation is, roughly: stable "has to work", ~arch "should work" and package.mask "might work, but..." |
 May be it would be more comfortable to have something like !arch for the last one? |
|
| Back to top |
|
|
Pythonhead
Developer
Joined: 16 Dec 2002
Posts: 1801
Location: Redondo Beach, Republic of Calif.
|
| Posted: Fri Jun 20, 2003 6:25 pm Post subject: |
|
|
| flurix wrote: | | Quote: | | Most are there because they haven't been properly tested. |
Interesting. I thought ~arch is the proper way of saying "it has not been tested, so
beware". And the portage mask is something like "don't use it as it won't compile,
install or work as expected (or not at all)". :? |
Well, I got that impression from reading the comments in the package.mask file. There are plenty that say "Do NOT use this package.", but it seems most need testing by developers before it goes to "~arch" |
|
| Back to top |
|
|
bsolar
Bodhisattva
Joined: 12 Jan 2003
Posts: 2764
|
| Posted: Fri Jun 20, 2003 6:48 pm Post subject: |
|
|
| flurix wrote: | | May be it would be more comfortable to have something like !arch for the last one? |
Uhm... the problem is that the kind of packages might be very different from package to package, there are some packages that "might work but..." and others that "don't work because..." or "I never tested it"...
Before merging these packages reading the commend is absolutely mandatory IMHO.
_________________
I may not agree with what you say, but I'll defend to the death your right to say it. |
|
| Back to top |
|
|
flurix
n00b
Joined: 24 Mar 2003
Posts: 26
|
| Posted: Fri Jun 20, 2003 6:57 pm Post subject: |
|
|
| Quote: | | before merging these packages reading the commend is absolutely mandatory IMHO. |
Absolutely agree. But I'm talking about the ease of use: the package is masked. Where? I know the tool grep but I also know less (the tool, I mean  ) |
|
| Back to top |
|
|
|
Portage & Programming
