[03:18] <wasabi> Need some packaging advice.
[03:18] <wasabi> I have totally altered /usr/share/eclipse and /usr/lib/eclipse. Mnay dirs turned to symlinks, many symlinks turned to dirs.
[03:18] <wasabi> dpkg of course plays havok with that.
[03:19] <jbailey_> Yeah.  dpkg will follow symlinks to install things.
[03:19] <wasabi> So how do I clean it up proper? I have come up with this less-than-stellar idea.
[03:20] <wasabi> Introduce 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] <wasabi> Eclipse's home has been moved to /usr/lib/eclipse
[03:20] <jbailey_> So you're just trying to preserve existing installs?
[03:20] <wasabi> Packages split into eclipse-feature, eclipse-feature-common and eclipse-feature-gcj
[03:20] <wasabi> No. I am just trying to make upgrading possible.
[03:21] <wasabi> -common stuff installs to /usr/share/eclipse
[03:21] <wasabi> non -common stuff installs into /usr/lib/eclipse, including a symlink farm in plugins pointing to /usr/share/eclipse/plugins
[03:21] <wasabi> (arch indep plugins)
[03:22] <wasabi> This is because Eclipse creates different plugins per arch.
[03:22] <jbailey_> Upgrading from what?
[03:22] <jbailey_> Current breezy
[03:22] <wasabi> Previous packages.
[03:22] <jbailey_> ?
[03:22] <wasabi> Yeah
[03:22] <jbailey_> Do the symlinks eventually go away?
[03:22] <wasabi> No.
[03:22] <jbailey_> If not, should eclipse simply be hacked to look in both places?
[03:23] <wasabi> I'd imagine that is pretty hard to do.
[03:23] <wasabi> Here's the thing. take eclipse-rcp
[03:23] <wasabi> It installs plugins/org.eclipse.swt.gtk.linux.x86/
[03:23] <wasabi> on ppc is's called ppc
[03:24] <jbailey_> That's /usr/lib/eclipse/... ?
[03:24] <wasabi> Yup.
[03:24] <wasabi> /usr/lib/eclipse/plugins
[03:24] <wasabi> My delima was I can't put a file named x86 in /usr/share
[03:24] <wasabi> Or 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:25] <wasabi> It used to.
[03:25] <wasabi> Last version's Eclipse home was /usr/share/eclipse.
[03:25] <wasabi> One dir, it can't search outside it for core plugins.
[03:25] <jbailey_> Ah, hmm.
[03:25] <wasabi> I can't explain this right can I?
[03:26] <jbailey_> No, I think I understand.
[03:26] <wasabi> Eclipse "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] <wasabi> Some core plugins are platform dependent.
[03:26] <wasabi> It actually works out pretty decently... it's just annoying on upgrade.
[03:27] <jbailey_> So do you symlink for each plugin then to the common directory?
[03:27] <wasabi> I could nix -common and install EVERYTHING to /usr/lib, but I wanted to put things in -common for archive space
[03:27] <wasabi> Yes. Correct.
[03:27] <wasabi> It's sort of like /usr/lib/X11
[03:27] <jbailey_> Yeah.
[03:27] <jbailey_> Except fUglier.
[03:28] <wasabi> Well, I wrote a 3 lines bash snippet to do it.
[03:28] <wasabi> hehe.
[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] <wasabi> Let me upload my packges for you
[03:29] <wasabi> I mean, I have it working... I just want advice on whether there's a better way.
[03:29] <wasabi> I 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] <wasabi> It has the concept, just not for core plugins.
[03:29] <wasabi> swt is a core one.
[03:31] <wasabi> http://akita.larvalstage.net/~wasabi/eclipse
[03:34] <jbailey> Much better.
[03:40] <wasabi> ANyways, with this trick, if you figure out how to get ppc compiling, it should work. :0
[03:42] <jbailey> Grab the .orig from the archive?
[03:42] <wasabi> Yes
[03:42] <bebop> hi
[03:42] <wasabi> hi
[03:43] <wasabi> Well, what I ended up doing is creating an eclipse-base package, which everything pre-depends on.
[03:43] <wasabi> I can define that as the base of all eclipse features, put the binary in it, etc.
[03:43] <jbailey> Err.  it's not in main?
[03:43] <wasabi> universe
[03:43] <jbailey> Cool, fetching.
[03:44] <bebop> im newbie of java and pbms are already raising: i have error in samples of xerces just downloaded
[03:44] <wasabi> And eclipse-base rm -rf's /usr/lib/eclipse and /usr/share/eclipse on clean install
[03:44] <wasabi> Which is fine since nobody has yet packaged any other plugins.
[03:44] <jbailey> Well.....
[03:44] <jbailey> The risk is clobbering something local that someone has done.
[03:44] <wasabi> Yeah.
[03:44] <jbailey> So it should really only be done on an upgrade, and if type can be narrowed, that would be great.
[03:45] <wasabi> I recognize it as a risk, but I don't think that at this stage it matters....
[03:45] <wasabi> First off, there's nothing people should be modifying in /usr/share/eclipse.
[03:45] <wasabi> jbailey, it's not an upgrade though.
[03:45] <jbailey> Right, but do thou not try to outthink the sysadmin, for he is mad and is therefore unpredictable.
[03:45] <wasabi> eclipse-base never previously existed.
[03:46] <jbailey> Yeah, hmm.
[03:46] <wasabi> I'm heading to work now. Let me know what you think. ;)
[03:46] <wasabi> bbs
[03:46] <jbailey> Will do, I'm just starting the build here on ppc.
[03:47] <wasabi> I know it won't work. Swt still doesn't build.
[03:47] <jbailey> Yeah, maybe I can convince it.
[03:47] <wasabi> But you are more than welcome to conquer that. ;)
[03:47] <wasabi> cya
[03:56] <jbailey> Compiling 484 source files to /home/jbailey/Programming/packaging/eclipse/eclipse-3.1/source-tree/plugins/org.eclipse.swt.win32.win32.x86/temp.folder/@dot.bin
[03:56] <jbailey> wtf?
[03:56] <jbailey> this is powerpc-linux...
[04:14] <mgalvin> hi all
[04:20] <robilad> hi mgalvin 
[04:20] <wasabi_> howdy
[04:23] <jbailey> wasabi_: /tmp/ccDIVnqk.s:5112275: Error: operand out of range (0x0000000000008000 is not
[04:23] <jbailey> between 0xffffffffffff8000 and 0x0000000000007fff)
[04:23] <jbailey> Is this what you were seeing on ppc?
[04:23] <wasabi_> gcj thing?
[04:23] <wasabi_> No. that's new.
[04:24] <wasabi_> What I was talking about was most likely a simple build script problem.
[04:56] <jbailey> Got some info from the gcj folks.  Seems there's a hack to aot-compile that we ought to be using to split jar files.
[05:32] <jbailey> wasabi_: Any objections to me updating aot-compile from java-gcj-compat and using it in eclipse?
[05:32] <wasabi_> Depends what aot-compile is
[05:33] <wasabi_> Never noticed it before.
[05:33] <jbailey> It's a jar to .so wrapper script.
[05:33] <wasabi_> Oh.
[05:33] <wasabi_> New to me.
[05:33] <wasabi_> No objection.
[05:34] <jbailey> Apparently it now splits jar files for compilation to work around this bug I'm seeing on ppc.
[05:45] <wasabi_> So you see my symlink stuff?
[05:49] <jbailey> I haven't got that far yet, sorry.
[05:50] <jbailey> I followed the conversation in #gcj while looking at some kernel stuff for Fabio.