On Wed, 25 Nov 2009 13:14:39 -0500
Marcus Wanner wrote:
> On 11/25/2009 12:20 PM, Chuck Robey wrote:
> > Mark Knecht wrote:
> >
> >> m...@dragonfly ~/Desktop $ eix eclipse
> >> * dev-java/ant-eclipse-ecj
> >> Available versions:
> >> (3.3) 3.3.0-r1
> >> (3.4) 3.4
> >> (3.5) ~3.5.1
> >> {elibc_FreeBSD}
> >> Homepage: http://www.eclipse.org/
> >> Description: Ant Compiler Adapter for Eclipse Java
> >> Compiler
> >>
> >>
> This shows that 3.5.1 is available, but is masked by a ~arch keyword.
> This means that the ebuild for 3.5.1 is not stable yet, and is not
> guaranteed to work (though it most likely will).
> >> * dev-java/eclipse-ecj
> >> Available versions:
> >> (3.3) 3.3.0-r3
> >> (3.4) 3.4-r4
> >> (3.5) ~3.5.1
> >> {ant elibc_FreeBSD java6}
> >> Homepage: http://www.eclipse.org/
> >> Description: Eclipse Compiler for Java
> >>
> >>
> Same for eclipse-ecj...
> >> * dev-util/eclipse-sdk
> >> Available versions: (3.4) 3.4-r2
> >> {doc elibc_FreeBSD java6}
> >> Homepage: http://www.eclipse.org/
> >> Description: Eclipse Tools Platform
> >>
> >>
> But not eclipse-sdk.
> >> dragonfly ~ # emerge -pv eclipse-ecj
> >>
> >> These are the packages that would be merged, in order:
> >>
> >> Calculating dependencies... done!
> >> [ebuild N ] app-admin/eselect-ecj-0.3 0 kB
> >> [ebuild N ] dev-java/eclipse-ecj-3.4-r4 USE="-java6" 1,251 kB
> >>
> >> Total: 2 packages (2 new), Size of downloads: 1,251 kB
> >>
> Here, he shows what would be installed if you ran "emerge elipse-ecj".
> >> dragonfly ~ # ACCEPT_KEYWORDS="~x86" emerge -pv eclipse-ecj
> >>
> >> These are the packages that would be merged, in order:
> >>
> >> Calculating dependencies... done!
> >> [ebuild N ] dev-python/pyxml-0.8.4-r2 USE="-doc -examples" 0
> >> kB [ebuild N ] dev-java/javatoolkit-0.3.0-r3 17 kB
> >> [ebuild N ] dev-java/ant-core-1.7.1-r4 USE="-doc -source"
> >> 6,828 kB [ebuild N ] app-admin/eselect-ecj-0.3 0 kB
> >> [ebuild N ] dev-java/eclipse-ecj-3.5.1 USE="ant" 1,268 kB
> >> [ebuild N ] dev-java/ant-eclipse-ecj-3.5.1 0 kB
> >>
> >> Total: 6 packages (6 new), Size of downloads: 8,111 kB
> >>
> This is what would happen if you temporarily told the system to allow
> the installation of ~arch packages. Temporarily setting ~arch is a
> Bad Idea!
> > I need to get an up-to-date version of eclipse working on my gentoo
> > box. First question is, is there a Galileo (3.5+) version of
> > eclipse available as a portage package? I can't find it, so I'd
> > really appreciate a pointer. The only thing I can see is a fairly
> > old eclipse version (I think a year or more out of date).
> That is because the newer version is keyworded with ~arch. Emerge
> will not tell you that there is a newer, keyworded version available.
> > Second question, at the eclipse website, I see a binary version of
> > the latest Linux-eclipse (the version I'm after). If I *can't* get
> > a portage package version of Galileo-eclipse,
> Don't worry, I'll show you how in a little bit!
> > then if I install the binary package (non-portage)
> > from the eclipse website, can I get (and how can I get) portage to
> > consider this package as supplying any dependency which would be
> > otherwise supplied by the latest (ganymede, 3.4+) portage version
> > of the eclipse tool>
> As far as I know of, that is not possible without ugly hacks.
> > Unless I'm completely misreading your stuff, your examples tell me
> > how to install the (too old) portage version, which is in all cases
> > just too old for me, so my 2 questions boil down to (1) must I?,
> > and (2) How do I?
> I don't know what you mean by "must I?", but the answer to "How do
> I?" is right here:
> First, you need to create a folder called /etc/portage as root. Then,
> create a file called package.keywords in that directory. When you
> want to install a keyworded package (dev-java/eclipse-ecj-3.5.1 in
> this case), you run
>
> ACCEPT_KEYWORDS="~x86" emerge -pv eclipse-ecj
>
> to see what packages are needed for the keyworded version. Then, you
> copy the the package names mentioned to package.keywords. In the
> example above, the command outputted:
>
> [ebuild N ] dev-python/pyxml-0.8.4-r2 USE="-doc -examples" 0 kB
> [ebuild N ] dev-java/javatoolkit-0.3.0-r3 17 kB
> [ebuild N ] dev-java/ant-core-1.7.1-r4 USE="-doc -source" 6,828
> kB [ebuild N ] app-admin/eselect-ecj-0.3 0 kB
> [ebuild N ] dev-java/eclipse-ecj-3.5.1 USE="ant" 1,268 kB
> [ebuild N ] dev-java/ant-eclipse-ecj-3.5.1 0 kB
>
> So you would add this:
>
> dev-python/pyxml-0.8.4-r2
> dev-java/javatoolkit-0.3.0-r3
> dev-java/ant-core-1.7.1-r4
> app-admin/eselect-ecj-0.3
> dev-java/eclipse-ecj-3.5.1
> dev-java/ant-eclipse-ecj-3.5.1
>
> to the package.keywords file (note that this will probably be
> different for your system, you should run the command yourself and
> use that output to find out what you should put in the file). I would
> also put a note above the lines to say why and when they were added,
> in case I forget.
>
> Then you can run "emerge -av eclipse-ecj" and see if it lists the new
> versions of everything.
>
> Marcus
Alternatively, one can use the autounmask command, for example:
autounmask dev-java/eclipse-ecj-3.5.1
On my AMD64 system, which has /etc/portage/package.keywords (as a
directory, rather than a file) autounmask generated file:
/etc/portage/package.keywords/autounmask-eclipse-ecj
which contains:
# ---
# BEGIN: dev-java/eclipse-ecj-3.5.1
# ---
=dev-java/eclipse-ecj-3.5.1 ~amd64
=dev-java/ant-eclipse-ecj-3.5.1 ~amd64
# ---
# END: dev-java/eclipse-ecj-3.5.1
# ---
HTH,
David
