1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On Friday 23 July 2004 06:41 pm, Michael Marineau wrote: |
5 |
> Michael Marineau wrote: |
6 |
> | I have a couple questions about why portage handles masked packages. |
7 |
> |
8 |
> oops, typo. *how* portage handles masked packages. |
9 |
> |
10 |
> | First of all, when a specific masked package is emerged (usually a |
11 |
> | ~mask) and |
12 |
> | it is depended on by another package emerge -UD world will fail because |
13 |
> | of the |
14 |
> | masked dependency. This can be avoided by specifically unmasking the |
15 |
> | package, |
16 |
> | but that can be a bit tedious if this situation is a common occurrence. |
17 |
> | Failing seems the right thing to do if the masked package is not already |
18 |
> | installed, but if the package is already installed it would make sense |
19 |
> | to me |
20 |
> | that portage realizes that the dependency is already met and not die. |
21 |
> | |
22 |
> | Another thought that I made a comment on in the GLEP 19 thread is that if |
23 |
> | a package is removed from the portage tree, later when upgrading another |
24 |
> | the user |
25 |
> | will be forced to upgrade(or downgrade if upgrades are masked) that |
26 |
> | package to, |
27 |
> | even if they wanted to keep the existing version. To get around this |
28 |
> | the user |
29 |
> | must save the old ebuild to their portage overly. I think it would make |
30 |
> | more |
31 |
> | sense to let the existing set of installed packages behave as another |
32 |
> | portage |
33 |
> | overly so that it is easy to hold on existing packages. This would also |
34 |
> | avoid |
35 |
> | any accidental downgrades if a package was ~arch masked, but then |
36 |
> | removed from |
37 |
> | portage in favor of a newer version. |
38 |
> | |
39 |
> | -- |
40 |
> | Michael Marineau |
41 |
> | marineam@×××××××××.edu |
42 |
> | Oregon State University |
43 |
|
44 |
man portage |
45 |
-----BEGIN PGP SIGNATURE----- |
46 |
Version: GnuPG v1.2.4 (GNU/Linux) |
47 |
|
48 |
iD8DBQFBAciU86Mtr34uz40RAnEfAJ92pg5GHPKJmNonlIm2xa3K2qxMiwCgrzMC |
49 |
SHijmj2wbA6rVLdnsPLJOk0= |
50 |
=3w2P |
51 |
-----END PGP SIGNATURE----- |
52 |
|
53 |
-- |
54 |
gentoo-dev@g.o mailing list |