1 |
On 11/25/2009 12:20 PM, Chuck Robey wrote: |
2 |
> Mark Knecht wrote: |
3 |
> |
4 |
>> mark@dragonfly ~/Desktop $ eix eclipse |
5 |
>> * dev-java/ant-eclipse-ecj |
6 |
>> Available versions: |
7 |
>> (3.3) 3.3.0-r1 |
8 |
>> (3.4) 3.4 |
9 |
>> (3.5) ~3.5.1 |
10 |
>> {elibc_FreeBSD} |
11 |
>> Homepage: http://www.eclipse.org/ |
12 |
>> Description: Ant Compiler Adapter for Eclipse Java Compiler |
13 |
>> |
14 |
>> |
15 |
This shows that 3.5.1 is available, but is masked by a ~arch keyword. |
16 |
This means that the ebuild for 3.5.1 is not stable yet, and is not |
17 |
guaranteed to work (though it most likely will). |
18 |
>> * dev-java/eclipse-ecj |
19 |
>> Available versions: |
20 |
>> (3.3) 3.3.0-r3 |
21 |
>> (3.4) 3.4-r4 |
22 |
>> (3.5) ~3.5.1 |
23 |
>> {ant elibc_FreeBSD java6} |
24 |
>> Homepage: http://www.eclipse.org/ |
25 |
>> Description: Eclipse Compiler for Java |
26 |
>> |
27 |
>> |
28 |
Same for eclipse-ecj... |
29 |
>> * dev-util/eclipse-sdk |
30 |
>> Available versions: (3.4) 3.4-r2 |
31 |
>> {doc elibc_FreeBSD java6} |
32 |
>> Homepage: http://www.eclipse.org/ |
33 |
>> Description: Eclipse Tools Platform |
34 |
>> |
35 |
>> |
36 |
But not eclipse-sdk. |
37 |
>> dragonfly ~ # emerge -pv eclipse-ecj |
38 |
>> |
39 |
>> These are the packages that would be merged, in order: |
40 |
>> |
41 |
>> Calculating dependencies... done! |
42 |
>> [ebuild N ] app-admin/eselect-ecj-0.3 0 kB |
43 |
>> [ebuild N ] dev-java/eclipse-ecj-3.4-r4 USE="-java6" 1,251 kB |
44 |
>> |
45 |
>> Total: 2 packages (2 new), Size of downloads: 1,251 kB |
46 |
>> |
47 |
Here, he shows what would be installed if you ran "emerge elipse-ecj". |
48 |
>> dragonfly ~ # ACCEPT_KEYWORDS="~x86" emerge -pv eclipse-ecj |
49 |
>> |
50 |
>> These are the packages that would be merged, in order: |
51 |
>> |
52 |
>> Calculating dependencies... done! |
53 |
>> [ebuild N ] dev-python/pyxml-0.8.4-r2 USE="-doc -examples" 0 kB |
54 |
>> [ebuild N ] dev-java/javatoolkit-0.3.0-r3 17 kB |
55 |
>> [ebuild N ] dev-java/ant-core-1.7.1-r4 USE="-doc -source" 6,828 kB |
56 |
>> [ebuild N ] app-admin/eselect-ecj-0.3 0 kB |
57 |
>> [ebuild N ] dev-java/eclipse-ecj-3.5.1 USE="ant" 1,268 kB |
58 |
>> [ebuild N ] dev-java/ant-eclipse-ecj-3.5.1 0 kB |
59 |
>> |
60 |
>> Total: 6 packages (6 new), Size of downloads: 8,111 kB |
61 |
>> |
62 |
This is what would happen if you temporarily told the system to allow |
63 |
the installation of ~arch packages. Temporarily setting ~arch is a Bad Idea! |
64 |
> I need to get an up-to-date version of eclipse working on my gentoo box. First |
65 |
> question is, is there a Galileo (3.5+) version of eclipse available as a portage |
66 |
> package? I can't find it, so I'd really appreciate a pointer. The only thing I |
67 |
> can see is a fairly old eclipse version (I think a year or more out of date). |
68 |
> |
69 |
That is because the newer version is keyworded with ~arch. Emerge will |
70 |
not tell you that there is a newer, keyworded version available. |
71 |
> Second question, at the eclipse website, I see a binary version of the latest |
72 |
> Linux-eclipse (the version I'm after). If I *can't* get a portage package |
73 |
> version of Galileo-eclipse, |
74 |
Don't worry, I'll show you how in a little bit! |
75 |
> then if I install the binary package (non-portage) |
76 |
> from the eclipse website, can I get (and how can I get) portage to consider this |
77 |
> package as supplying any dependency which would be otherwise supplied by the |
78 |
> latest (ganymede, 3.4+) portage version of the eclipse tool> |
79 |
> |
80 |
As far as I know of, that is not possible without ugly hacks. |
81 |
> Unless I'm completely misreading your stuff, your examples tell me how to |
82 |
> install the (too old) portage version, which is in all cases just too old for |
83 |
> me, so my 2 questions boil down to (1) must I?, and (2) How do I? |
84 |
> |
85 |
I don't know what you mean by "must I?", but the answer to "How do I?" |
86 |
is right here: |
87 |
First, you need to create a folder called /etc/portage as root. Then, |
88 |
create a file called package.keywords in that directory. When you want |
89 |
to install a keyworded package (dev-java/eclipse-ecj-3.5.1 in this |
90 |
case), you run |
91 |
|
92 |
ACCEPT_KEYWORDS="~x86" emerge -pv eclipse-ecj |
93 |
|
94 |
to see what packages are needed for the keyworded version. Then, you |
95 |
copy the the package names mentioned to package.keywords. In the example |
96 |
above, the command outputted: |
97 |
|
98 |
[ebuild N ] dev-python/pyxml-0.8.4-r2 USE="-doc -examples" 0 kB |
99 |
[ebuild N ] dev-java/javatoolkit-0.3.0-r3 17 kB |
100 |
[ebuild N ] dev-java/ant-core-1.7.1-r4 USE="-doc -source" 6,828 kB |
101 |
[ebuild N ] app-admin/eselect-ecj-0.3 0 kB |
102 |
[ebuild N ] dev-java/eclipse-ecj-3.5.1 USE="ant" 1,268 kB |
103 |
[ebuild N ] dev-java/ant-eclipse-ecj-3.5.1 0 kB |
104 |
|
105 |
So you would add this: |
106 |
|
107 |
dev-python/pyxml-0.8.4-r2 |
108 |
dev-java/javatoolkit-0.3.0-r3 |
109 |
dev-java/ant-core-1.7.1-r4 |
110 |
app-admin/eselect-ecj-0.3 |
111 |
dev-java/eclipse-ecj-3.5.1 |
112 |
dev-java/ant-eclipse-ecj-3.5.1 |
113 |
|
114 |
to the package.keywords file (note that this will probably be different |
115 |
for your system, you should run the command yourself and use that output |
116 |
to find out what you should put in the file). I would also put a note |
117 |
above the lines to say why and when they were added, in case I forget. |
118 |
|
119 |
Then you can run "emerge -av eclipse-ecj" and see if it lists the new |
120 |
versions of everything. |
121 |
|
122 |
Marcus |