| View previous topic :: View next topic |
| Author |
Message |
D-M
Tux's lil' helper
Joined: 23 Jan 2004
Posts: 103
|
 Posted: Tue Jun 28, 2005 10:44 pm Post subject: manually installing sun jdk |
 |
|
One of the developers here at work wrote a small java application that we need to test running under Linux. I would like to use Gentoo for this, but unfortunately the jdk this application was built against is newer then what is in portage. Ideally I would like to test it against the same version of jdk it was build with. I have searched the forums and could not find (doesn't mean it isn't there, just didn't find it) any tips or directions for confirming what I believe the steps are for manually installing a newer jdk. If I understand what little I did find correctly the steps are
extract the jdk to /opt
modify the java entries in env.d
run the jave-config tool
As far as the files in env.d go, do I need to modify both the 20java file and create a file in java directory or just create the file in the java directory for the new jdk? I am thinking I just need to build the file in the java directory but wanted to be sure.
I do understand that this can cause problems latter if we were to then try and upgrade using portage or that many applications in portage still do not compile against the the 1.5.x jdk/jre, we will worry about those issues later if the application runs as hoped.
DM |
|
| Back to top |
|
 |
Flammie
Retired Dev
Joined: 02 Jun 2003
Posts: 633
Location: Dublin, Ireland
|
| Posted: Tue Jun 28, 2005 10:57 pm Post subject: Re: manually installing sun jdk |
|
|
| D-M wrote: | | One of the developers here at work wrote a small java application that we need to test running under Linux. I would like to use Gentoo for this, but unfortunately the jdk this application was built against is newer then what is in portage. |
Portage has up to 1.5.0.04, are you using unreleased version of jdk with your project? The 1.5.0 is masked though, in order to unmask you'll need to add it to /etc/portage/package.unmask. |
|
| Back to top |
|
|
D-M
Tux's lil' helper
Joined: 23 Jan 2004
Posts: 103
|
| Posted: Tue Jun 28, 2005 11:17 pm Post subject: |
|
|
wow 1.5.4 wasn't there yesterday, the java team sure moves fast.
1.5.0.02 is the version it was built against, which is hard masked, which I understand can't be overcome even by package.keywords.
DM |
|
| Back to top |
|
|
jonnevers
Veteran
Joined: 02 Jan 2003
Posts: 1594
Location: Gentoo64 land
|
| Posted: Wed Jun 29, 2005 2:06 am Post subject: |
|
|
| D-M wrote: | wow 1.5.4 wasn't there yesterday, the java team sure moves fast.
1.5.0.02 is the version it was built against, which is hard masked, which I understand can't be overcome even by package.keywords.
DM |
unless you are working around specific bugs, you should probably stablize upon a major point release. say 1.4.2 or 1.5.
I constantly rebuild java applications, installed jdk is 1.4.2-6, required platform for deployment is 1.4.2.
- Jon |
|
| Back to top |
|
|
catzooka
Apprentice
Joined: 05 Nov 2002
Posts: 193
|
| Posted: Wed Jun 29, 2005 3:05 am Post subject: |
|
|
| D-M wrote: | wow 1.5.4 wasn't there yesterday, the java team sure moves fast.
1.5.0.02 is the version it was built against, which is hard masked, which I understand can't be overcome even by package.keywords.
DM |
Actually, you can bypass the hard mask, by adding the package to package.keywords, as well as, package.mask.
| Code: | echo "=category/package-version" >> /etc/portage/package.mask
echo "=category/package-version ~x86" >> /etc/portage/package.keywords |
|
|
| Back to top |
|
|
D-M
Tux's lil' helper
Joined: 23 Jan 2004
Posts: 103
|
| Posted: Wed Jun 29, 2005 4:44 am Post subject: |
|
|
| jonnevers wrote: | | D-M wrote: | wow 1.5.4 wasn't there yesterday, the java team sure moves fast.
1.5.0.02 is the version it was built against, which is hard masked, which I understand can't be overcome even by package.keywords.
DM |
unless you are working around specific bugs, you should probably stablize upon a major point release. say 1.4.2 or 1.5.
I constantly rebuild java applications, installed jdk is 1.4.2-6, required platform for deployment is 1.4.2.
- Jon |
Good advice, unfortunatly it wasn't my call. But ya we are working on a bug.
DM |
|
| Back to top |
|
|
D-M
Tux's lil' helper
Joined: 23 Jan 2004
Posts: 103
|
| Posted: Wed Jun 29, 2005 4:47 am Post subject: |
|
|
| Deftochino wrote: | | D-M wrote: | wow 1.5.4 wasn't there yesterday, the java team sure moves fast.
1.5.0.02 is the version it was built against, which is hard masked, which I understand can't be overcome even by package.keywords.
DM |
Actually, you can bypass the hard mask, by adding the package to package.keywords, as well as, package.mask.
| Code: | echo "=category/package-version" >> /etc/portage/package.mask
echo "=category/package-version ~x86" >> /etc/portage/package.keywords |
|
the docs seemed to indicate just doing the ~x86 unmask would expose the hard mask, but then other docs seems to make it sound like you could not get around a hard mask.
I will try exactly as you suggest and let you know.
thanks for the tip and clarification.
DM |
|
| Back to top |
|
|
catzooka
Apprentice
Joined: 05 Nov 2002
Posts: 193
|
| Posted: Wed Jun 29, 2005 1:44 pm Post subject: |
|
|
| It all depends on the package. Hardmasked packages are those that are not only masked by an ~arch keyword (like ~x86), but also by an entry in /usr/portage/profiles/package.mask. Other packages might just be masked by the ~arch keyword, in which case adding them to package.keywords will suffice. Hardmasked packages will require both an entry in package.mask and package.keywords for you to be able to emerge them. |
|
| Back to top |
|
|
D-M
Tux's lil' helper
Joined: 23 Jan 2004
Posts: 103
|
| Posted: Wed Jun 29, 2005 11:01 pm Post subject: |
|
|
| Deftochino wrote: |
Actually, you can bypass the hard mask, by adding the package to package.keywords, as well as, package.mask.
| Code: | echo "=category/package-version" >> /etc/portage/package.mask
echo "=category/package-version ~x86" >> /etc/portage/package.keywords |
|
This did not work, but by changing the first line from package.mask to package.unmask did
once I did that when I did and emerge -p package, the newer hard masked jdk was available. I now have the newer JDk install
and can now test the application against it. I am going to suggest that once that test is over we test against the stable jdk in portage.
since the application is a simple one it should work (keeps fingers crossed).
thanks everyone for your help in getting me going in the right direction.
DM |
|
| Back to top |
|
|
catzooka
Apprentice
Joined: 05 Nov 2002
Posts: 193
|
| Posted: Thu Jun 30, 2005 12:07 am Post subject: |
|
|
haha. yeah. I'm sorry, it must have been late. Of course it has to be package.unmask. I'm sorry, the hardmasks are put into /usr/portage/profiles/package.mask, while unmasking them requires an entry in package.unmask. Sorry, about the confusion.  |
|
| Back to top |
|
|
|
Other Things Gentoo
