| 1 |
I've been working through about 130 packages to gen2 using prefix'd |
| 2 |
builds (EAPI="prefix"), it was an interesting challenge to move |
| 3 |
everything to JDK 5.0 and I have a few fixes and new ebuilds etc to |
| 4 |
commit somewhere. I have the following thoughts on making JDK 5 stable. |
| 5 |
|
| 6 |
1. source vs jars ebuilds. |
| 7 |
I built everything from source minus one jar file. I had to drop to |
| 8 |
source 1.4 or patch the code in some cases. However some projects are |
| 9 |
based on maven jar repositories, getting a source version of these can |
| 10 |
be a huge project in itself. |
| 11 |
|
| 12 |
2. Using open source components vs certified binary components. |
| 13 |
Downloading certified jars from Sun or other vendors was a pain, however |
| 14 |
picking up a free implementation that may have never been certified may |
| 15 |
be just as bad if you don't know what you are doing (and caused a long |
| 16 |
tail of dependencies of cause) |
| 17 |
|
| 18 |
3. Varying dependencies |
| 19 |
I ended up with a very simple hibernate 3.1 ebuild for example, the |
| 20 |
current migration ebuild essentially pulls in the rest of jboss |
| 21 |
|
| 22 |
regards |
| 23 |
calvin |
| 24 |
|
| 25 |
Krzysiek Pawlik wrote: |
| 26 |
|
| 27 |
>As of now all packages ported to generation 2 are moved from |
| 28 |
>gentoo-java-experimental to migration-packages. |
| 29 |
> |
| 30 |
>Any new migrated package has to be moved to migration-packages as well. |
| 31 |
>It will ease integration of ported packages into the portage tree. |
| 32 |
> |
| 33 |
> |
| 34 |
> |
| 35 |
|
| 36 |
-- |
| 37 |
gentoo-java@g.o mailing list |
Archives