| 1 |
Ben Munat wrote: |
| 2 |
> Hello, |
| 3 |
> |
| 4 |
> Does anyone know what the story is with the deprecation of the |
| 5 |
> --upgradeonly option on emerge? The emerge man page says: |
| 6 |
> |
| 7 |
> "This option is deprecated and shouldn't be used anymore. Please use the |
| 8 |
> /etc/portage/package.* files from now on." |
| 9 |
> |
| 10 |
> but it doesn't say what these package.* files are supposed to be. None |
| 11 |
> of my gentoo systems have any package.* files in the /etc/portage |
| 12 |
> directory. |
| 13 |
> |
| 14 |
> Also the announcement page on the gentoo site talks about several other |
| 15 |
> new features, but doesn't discuss this deprecation. |
| 16 |
> |
| 17 |
> I am using a few packages that are masked and I don't want portage to |
| 18 |
> revert to an earlier version. The --upgradeonly switch was nice and |
| 19 |
> easy... don't know why the devs had to screw with that. |
| 20 |
|
| 21 |
You have to create files in /etc/portage if you want to use them. For example, |
| 22 |
if you want to unmask a version of a package that is hard masked, you would |
| 23 |
create 'package.unmask' and add something like: |
| 24 |
|
| 25 |
pkg-cat/pkg |
| 26 |
=pkg-cat/pkg-3.2-r1 |
| 27 |
>pkg-cat/pkg-3.4 |
| 28 |
|
| 29 |
If you are running ACCEPT_KEYWORDS="x86" and want a ~x86 package, you can create |
| 30 |
'package.keywords' and add something like: |
| 31 |
|
| 32 |
pkg-cat/pkg ~x86 |
| 33 |
=pkg-cat/pkg-3.2-r1 ~x86 |
| 34 |
>pkg-cat/pkg-3.4 |
| 35 |
|
| 36 |
If you have a package installed that doesn't fit in these 2 categories and |
| 37 |
Portage wants to downgrade it, it is probably because it was masked due to a |
| 38 |
serious security problem or the version has a bad bug that was only discovered |
| 39 |
after it went into the tree. |
| 40 |
|
| 41 |
-- |
| 42 |
Andrew Gaffney |
| 43 |
Network Administrator |
| 44 |
Skyline Aeronautics, LLC. |
| 45 |
636-357-1548 |
Archives