/srv/irclogs.ubuntu.com/2005/07/16/#ubuntu-java.txt

=== wasabi [~wasabi@c-67-174-81-195.hsd1.tx.comcast.net] has joined #ubuntu-java
=== jbailey [~jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-java
=== ChanServ [ChanServ@services.] has joined #ubuntu-java
=== wasabi [~wasabi@c-67-174-81-195.hsd1.tx.comcast.net] has joined #ubuntu-java
=== netjoined: irc.freenode.net -> kornbluth.freenode.net
=== topic_ [~topic@mpiat2305.ag2.mpi-sb.mpg.de] has joined #ubuntu-java
=== jbailey [~jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-java
=== wasabi [~wasabi@c-67-174-81-195.hsd1.tx.comcast.net] has joined #ubuntu-java
=== wasabi [~wasabi@c-67-174-81-195.hsd1.tx.comcast.net] has joined #ubuntu-java
=== doko [~doko@a130-233-5-210.debconf5.hut.fi] has joined #ubuntu-java
=== jbailey_ [~jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-java
=== ChanServ [ChanServ@services.] has joined #ubuntu-java
wasabiNeed some packaging advice.03:18
wasabiI have totally altered /usr/share/eclipse and /usr/lib/eclipse. Mnay dirs turned to symlinks, many symlinks turned to dirs.03:18
wasabidpkg of course plays havok with that.03:18
jbailey_Yeah.  dpkg will follow symlinks to install things.03:19
wasabiSo how do I clean it up proper? I have come up with this less-than-stellar idea.03:19
wasabiIntroduce a new "eclipse-base" package and have it rmdir /usr/share/eclipse and /usr/lib/eclipse on clean install.03:20
jbailey_First can you tell me why there's a symlink farm?03:20
wasabiEclipse's home has been moved to /usr/lib/eclipse03:20
jbailey_So you're just trying to preserve existing installs?03:20
wasabiPackages split into eclipse-feature, eclipse-feature-common and eclipse-feature-gcj03:20
wasabiNo. I am just trying to make upgrading possible.03:20
wasabi-common stuff installs to /usr/share/eclipse03:21
wasabinon -common stuff installs into /usr/lib/eclipse, including a symlink farm in plugins pointing to /usr/share/eclipse/plugins03:21
wasabi(arch indep plugins)03:21
wasabiThis is because Eclipse creates different plugins per arch.03:22
jbailey_Upgrading from what?03:22
jbailey_Current breezy03:22
wasabiPrevious packages.03:22
jbailey_?03:22
wasabiYeah03:22
jbailey_Do the symlinks eventually go away?03:22
wasabiNo.03:22
jbailey_If not, should eclipse simply be hacked to look in both places?03:22
wasabiI'd imagine that is pretty hard to do.03:23
wasabiHere's the thing. take eclipse-rcp03:23
wasabiIt installs plugins/org.eclipse.swt.gtk.linux.x86/03:23
wasabion ppc is's called ppc03:23
jbailey_That's /usr/lib/eclipse/... ?03:24
wasabiYup.03:24
wasabi/usr/lib/eclipse/plugins03:24
wasabiMy delima was I can't put a file named x86 in /usr/share03:24
wasabiOr I'd have to put the files named ppc and ppc64 and amd64 blah blah in there also.03:24
jbailey_But eclipse expects to find things in /usr/share/eclipse/plugins/org... ?03:24
wasabiIt used to.03:25
wasabiLast version's Eclipse home was /usr/share/eclipse.03:25
wasabiOne dir, it can't search outside it for core plugins.03:25
jbailey_Ah, hmm.03:25
wasabiI can't explain this right can I?03:25
jbailey_No, I think I understand.03:26
wasabiEclipse "lives" in one directory. It expects to have the core plugins there.03:26
jbailey_I'm just trying to think of a way to solve this without needing a symlink farm.03:26
wasabiSome core plugins are platform dependent.03:26
wasabiIt actually works out pretty decently... it's just annoying on upgrade.03:26
jbailey_So do you symlink for each plugin then to the common directory?03:27
wasabiI could nix -common and install EVERYTHING to /usr/lib, but I wanted to put things in -common for archive space03:27
wasabiYes. Correct.03:27
wasabiIt's sort of like /usr/lib/X1103:27
jbailey_Yeah.03:27
jbailey_Except fUglier.03:27
wasabiWell, I wrote a 3 lines bash snippet to do it.03:28
wasabihehe.03:28
jbailey_Sounds like my mother in law is awake, I might be able to use the main terminal now, just a sec.03:28
wasabiLet me upload my packges for you03:28
wasabiI mean, I have it working... I just want advice on whether there's a better way.03:29
wasabiI really don't fancy hacking around in Eclipse to solve it.03:29
jbailey_The only thing better would be to teach eclipse the concept of looking in multiple places.03:29
wasabiIt has the concept, just not for core plugins.03:29
wasabiswt is a core one.03:29
wasabihttp://akita.larvalstage.net/~wasabi/eclipse03:31
jbaileyMuch better.03:34
wasabiANyways, with this trick, if you figure out how to get ppc compiling, it should work. :003:40
jbaileyGrab the .orig from the archive?03:42
wasabiYes03:42
=== bebop [~boris@suc94-2-82-230-13-211.fbx.proxad.net] has joined #ubuntu-java
bebophi03:42
wasabihi03:42
wasabiWell, what I ended up doing is creating an eclipse-base package, which everything pre-depends on.03:43
wasabiI can define that as the base of all eclipse features, put the binary in it, etc.03:43
jbaileyErr.  it's not in main?03:43
wasabiuniverse03:43
jbaileyCool, fetching.03:43
bebopim newbie of java and pbms are already raising: i have error in samples of xerces just downloaded03:44
wasabiAnd eclipse-base rm -rf's /usr/lib/eclipse and /usr/share/eclipse on clean install03:44
wasabiWhich is fine since nobody has yet packaged any other plugins.03:44
jbaileyWell.....03:44
jbaileyThe risk is clobbering something local that someone has done.03:44
wasabiYeah.03:44
jbaileySo it should really only be done on an upgrade, and if type can be narrowed, that would be great.03:44
wasabiI recognize it as a risk, but I don't think that at this stage it matters....03:45
wasabiFirst off, there's nothing people should be modifying in /usr/share/eclipse.03:45
wasabijbailey, it's not an upgrade though.03:45
jbaileyRight, but do thou not try to outthink the sysadmin, for he is mad and is therefore unpredictable.03:45
wasabieclipse-base never previously existed.03:45
jbaileyYeah, hmm.03:46
wasabiI'm heading to work now. Let me know what you think. ;)03:46
wasabibbs03:46
jbaileyWill do, I'm just starting the build here on ppc.03:46
wasabiI know it won't work. Swt still doesn't build.03:47
jbaileyYeah, maybe I can convince it.03:47
wasabiBut you are more than welcome to conquer that. ;)03:47
wasabicya03:47
jbaileyCompiling 484 source files to /home/jbailey/Programming/packaging/eclipse/eclipse-3.1/source-tree/plugins/org.eclipse.swt.win32.win32.x86/temp.folder/@dot.bin03:56
jbaileywtf?03:56
jbaileythis is powerpc-linux...03:56
=== topic_ is now known as robilad
=== mgalvin [~mgalvin@host-66-202-95-170.spr.choiceone.net] has joined #ubuntu-java
mgalvinhi all04:14
=== wasabi_ [~wasabi@207.55.180.100] has joined #ubuntu-java
robiladhi mgalvin 04:20
wasabi_howdy04:20
jbaileywasabi_: /tmp/ccDIVnqk.s:5112275: Error: operand out of range (0x0000000000008000 is not04:23
jbaileybetween 0xffffffffffff8000 and 0x0000000000007fff)04:23
jbaileyIs this what you were seeing on ppc?04:23
wasabi_gcj thing?04:23
wasabi_No. that's new.04:23
wasabi_What I was talking about was most likely a simple build script problem.04:24
jbaileyGot some info from the gcj folks.  Seems there's a hack to aot-compile that we ought to be using to split jar files.04:56
jbaileywasabi_: Any objections to me updating aot-compile from java-gcj-compat and using it in eclipse?05:32
wasabi_Depends what aot-compile is05:32
wasabi_Never noticed it before.05:33
jbaileyIt's a jar to .so wrapper script.05:33
wasabi_Oh.05:33
wasabi_New to me.05:33
wasabi_No objection.05:33
jbaileyApparently it now splits jar files for compilation to work around this bug I'm seeing on ppc.05:34
wasabi_So you see my symlink stuff?05:45
jbaileyI haven't got that far yet, sorry.05:49
jbaileyI followed the conversation in #gcj while looking at some kernel stuff for Fabio.05:50
=== doko [~doko@a130-233-5-210.debconf5.hut.fi] has joined #ubuntu-java
=== wasabi_ [~wasabi@207.55.180.100] has joined #ubuntu-java
=== yourghetek [~user@c-67-174-254-167.hsd1.ca.comcast.net] has joined #ubuntu-java
=== yourghetek [~user@c-67-174-254-167.hsd1.ca.comcast.net] has left #ubuntu-java []

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!