| 1 |
> One way to do it: remove whatever packages you do not want touched by |
| 2 |
> "world" out of /var/cache/edb/world. The packages in that file are the |
| 3 |
> only ones that will get looked at whenever you run 'emerge -u world'. |
| 4 |
|
| 5 |
Well there is two problems with this approach. First one is that by |
| 6 |
removing this package from the world file it will not be updated anymore |
| 7 |
when a new version (newer than the one installed) is released. Second |
| 8 |
problem is that this hack won't work if the package removed from the world |
| 9 |
file is required as a dependency for another package you're trying to |
| 10 |
install. Portage will resolve the denpendency, will want to install your |
| 11 |
package and will downgrade it. |
| 12 |
|
| 13 |
> Secondarily, I suggest running 'emerge -up world' to see what would be |
| 14 |
> downgraded first, without actually running anything. |
| 15 |
> |
| 16 |
> Automatic downgrading is generally healthy behavior (if for example, we |
| 17 |
> unmasked a new version which later proved broken/unstable, therefore we |
| 18 |
> need people to revert to an older, stable release). |
| 19 |
|
| 20 |
Yes but there should be a way to disable this. An option to "pin" a |
| 21 |
minimum version of a package or to simply disable the possibility of |
| 22 |
downgrading a package (with a switch on the command line or better, a |
| 23 |
configurable option in /etc/make.conf). |
| 24 |
|
| 25 |
The case you are talking about *should* pratically never happen if |
| 26 |
packages we're tested *before* being released. |
| 27 |
|
| 28 |
> This is a FAQ... I'm sure there are some enhancements to Portage |
| 29 |
> underway which will make this issue more elegant/intuitive. |
| 30 |
|
| 31 |
I really hope the Gentoo developpers will add this functionnality. Ever |
| 32 |
since the introduction for the ~arch keywords packages updates have been a |
| 33 |
mess for me. If you are running on a stable system exclusively everything |
| 34 |
is fine. Same thing if you are running exclusively with an unstable system |
| 35 |
(with ~arch). If you never use the emerge world command you should not |
| 36 |
have many problems, just define the ACCEPT_KEYWORDS before emerging |
| 37 |
unstable packages and you're ok. |
| 38 |
|
| 39 |
The problem comes when you are using stable *and* unstable *and* emerge |
| 40 |
world command. Try to emerge world a mix of stable and unstable packages |
| 41 |
and see all the packages downgrades. Try to define ACCEPT_KEYWORDS, now |
| 42 |
Portage wants to install all unstable packages. Mask the old version of |
| 43 |
unstable packages you installed (or just remove them from the world file) |
| 44 |
and watch Portage trying to resolve a dependency for another packages and |
| 45 |
downgrade your package anyway... The only thing Portage need is a |
| 46 |
"don't-ever-downgrade-my-packages" function IMHO. |
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
-- |
| 51 |
gentoo-dev@g.o mailing list |
Archives