I actually ended up installing outside the root. I hadn't thought of touching the other files.
There was also a problem in one of my shells when only the JAVA_HOME was set. I think this broke some of the wrapper logic. Is there some way we could automate the RPM and grab the sources on the fly like wrapper packages on some of the distributions do? I would be nice to make this process a lot cleaner. I know this could be difficult due to licensing/click-through. I, for one, would like openpkg to appeal to small-installation folks who might not have the patience to work through some of these problems. For instance, ubuntu 8.04 doesn't have subversion 1.5 and I'd love to just tell people to use openpkg. I also signed the contributor agreement, so I'd like to update java-jdk16 to u10 and fix a typo in the name of the docs zip. -Dave On Fri, Oct 31, 2008 at 5:51 PM, Ralf S. Engelschall <[EMAIL PROTECTED]>wrote: > On Fri, Oct 31, 2008, David Stenglein wrote: > > > I am having problems "building" the java-jdk15 and java-jdk16. It seems > to want > > the sources for all platforms due to the %setup macro. What is the > procedure > > for installing java for a single platform? > > Well, just touch(1) the remaining SourceX files on the filesystem. > OpenPKG RPM is happy if the files just exist. Only those who belong to > your particular platform have to be real files. The other possibility > is to install a JDK totally manually and outside of OpenPKG into > /path/to/jdk and then install the "java-jdkfake" package plus running > "java-toolkit --register=sun-jdk-fake:/path/to/jdk". This also will > satisfy all Java dependencies within OpenPKG. > > Ralf S. Engelschall > [EMAIL PROTECTED] > www.engelschall.com > > ______________________________________________________________________ > OpenPKG http://openpkg.org > User Communication List openpkg-users@openpkg.org >
