View previous topic :: View next topic |
Author |
Message |
/ n00b
Joined: 14 Aug 2002 Posts: 26
|
Posted: Fri Oct 25, 2002 9:43 am Post subject: How does emerge consider what version to merge? |
|
|
Hi,
In media-gfx/imagemagick there are the following files:
Code: | media-gfx/imagemagick/imagemagick-5.4.7.ebuild
media-gfx/imagemagick/imagemagick-5.4.7-r1.ebuild
media-gfx/imagemagick/imagemagick-5.4.7-r2.ebuild
media-gfx/imagemagick/imagemagick-5.4.9.1.ebuild
|
when i do emerge imagemagick I get:
Code: |
portage # emerge -p imagemagick
These are the packages that I would merge, in order.
Calculating dependencies ...done!
[ebuild N ] media-gfx/imagemagick-5.4.7-r2
|
Now what I am trying to figure out is how emerge comes to the decision not to install the latest version. Apart from that the ebuild for 5.4.7-r2 is broken, as the sourcefile is no longer available...
I've been looking for a file where imagemagick was masked. (Amongst others by doing a grep -l -r imagemagick in /usr/portage). I could not find any.
So my question is the following: What other files/data/influences etc. can make emerge not to install the latest version of ImageMagick in this case, and how does emerge go at deciding what version to install of a package in general.
[/code] |
|
Back to top |
|
|
jondkent Apprentice
Joined: 26 Jul 2002 Posts: 289 Location: London
|
Posted: Fri Oct 25, 2002 9:46 am Post subject: |
|
|
Hi,
the mask file is in:
Code: |
/usr/portage/profiles/package.mask
|
although I cannot find imagemagick in it which is werid
Jon |
|
Back to top |
|
|
jondkent Apprentice
Joined: 26 Jul 2002 Posts: 289 Location: London
|
Posted: Fri Oct 25, 2002 9:53 am Post subject: |
|
|
Think I found the problem.
If you look at the ebuild for 5.4.9.1 you'll see a KEYWORD section which expects ~x86 ~ppc or ~sparc64. So this package is not considered stable. To install it add the following into your make.conf file
Code: |
ACCEPT_KEYWORDS="~x86"
|
and it will install. You may wish to comment this out after the install to ensure the rest are kept at stable. Or I think you can do this
Code: |
export ACCEPT_KEYWORDS="~x86"
|
as a more temporary measure
Jon |
|
Back to top |
|
|
|