Ubuntu 8.10/Intrepid and openpkg.
I wanted to report on my experience installing openpkg on ubuntu 8.10. The main issue was the compiler upgrade to gcc 4.3. I was able to install gcc 4.2 and do a bootstrap by specifying the compiler explicitly. The real issue came when I wanted install other packages after the bootstrap. It doesn't seem easy to override the compiler of all of the various packages, so I had to do a little tweak. I uninstalled gcc4.3 and made a symbolic for gcc and cc and then everything built just fine. lrwxrwxrwx 1 root root 7 2008-11-05 23:42 /usr/bin/gcc - gcc-4.2 lrwxrwxrwx 1 root root 7 2008-11-05 23:43 /usr/bin/cc - gcc-4.2 I didn't uninstall these links after building gcc, so I don't know if all of the other packages would install okay without the symbolic links at that point (they should, I assume). Would it be possible to add gcc to the bootstrap process to alleviate this? Either that, or having the binary bootstraps available. BTW, the documentation should be fixed to remove the binary bootstrap instructions (unless the binaries will be coming back at some point). -Dave
Maven package problem.
The mvn/maven.sh seems to be based on the new java infrastructure, but it seems to have a problem. The line at the beginning: export JAVA_PLATFORM=sun-jdk seems to throw things off. Should this just be removed? -Dave
Re: How to copy configuration between instances/platforms.
Well, it took a year and a half, but I finally got around to this. ;-) I did an upgrade from ubuntu 8.04 to ubuntu 8.10. Not a huge switch, but I reinstalled openpkg from scratch, so it's about the same as changing platforms. I followed the instructions from Thomas and it pretty much worked. The only thing I had to do was capture the script and run a sed to convert the platform parts of package names to use the new platform. Maybe the scripts could be generated to use a variable for this, making the process even more trivial? Even easier would be specifying a target architecture for the script. Of course, this is just for binary package matching. I haven't done anything for configuration related data yet. -Dave On Fri, Mar 16, 2007 at 3:26 PM, David Stenglein [EMAIL PROTECTED]wrote: Thomas, Thanks very much for all of the infomation. Work has been busy this week and I hope to look at all of this some more this weekend. -Dave On 3/15/07, Thomas Lotterer [EMAIL PROTECTED] wrote: cloning OpenPKG: bootstrap http://www.lotterer.net/blog/en/41 cloning OpenPKG: packages http://www.lotterer.net/blog/en/42 cloning OpenPKG: configuration http://www.lotterer.net/blog/en/43 There is potential for more work. Some applications store configuration information in non-text files, e.g. databases, requiring additional adoption steps. Worse, some binary data formats are platform dependent, e.g. because of locale settings or CPU data width or byte order, requiring conversion or export/import procedures. -- http://thomas.lotterer.net __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: Maven package problem.
On Thu, Nov 13, 2008, David Stenglein wrote: The mvn/maven.sh seems to be based on the new java infrastructure, but it seems to have a problem. The line at the beginning: export JAVA_PLATFORM=sun-jdk seems to throw things off. Should this just be removed? Sorry, can you be more specific: what do you mean by throw things off? The JAVA_PLATFORM variable just says that the Java has to be a JDK (and not GCJ, etc) because (as I can remember) that Maven didn't work with GCJ. What does break for you? Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
Re: Maven package problem.
Actually, the problem has more to do with a mixed up environment. I'm not sure I would call it a bug, but it was a bit confusing: charm% env | grep JAVA JAVA_HOME=/openpkg/libexec/java-jdk15 JAVA_PLATFORM=sun-jdk-1.5.0 charm% unset JAVA_PLATFORM charm% mvn.orig /openpkg/bin/java:ERROR: invalid JAVA_PLATFORM: sun-jdk charm% Now that I have openpkg fully merged into my environment, this doesn't happen. But before, when I was using /openpkg/bin/mvn with my normal environment, which just had JAVA_HOME set, I would get this error. It's a little strange because this would only happen within maven. If you run java directly (no args) it doesn't complain. I'll try to take a closer look when I get a chance. -Dave On Thu, Nov 13, 2008 at 1:57 PM, Ralf S. Engelschall [EMAIL PROTECTED]wrote: On Thu, Nov 13, 2008, David Stenglein wrote: The mvn/maven.sh seems to be based on the new java infrastructure, but it seems to have a problem. The line at the beginning: export JAVA_PLATFORM=sun-jdk seems to throw things off. Should this just be removed? Sorry, can you be more specific: what do you mean by throw things off? The JAVA_PLATFORM variable just says that the Java has to be a JDK (and not GCJ, etc) because (as I can remember) that Maven didn't work with GCJ. What does break for you? Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com __ OpenPKG http://openpkg.org User Communication List openpkg-users@openpkg.org
