Oops, I meant to CC the list.
Hi Ben,
* Benjamin Pasero bpasero@rssowl.org [2005-07-25 15:58]:
the origin of this is most likely "jface.jar" requring parts of Eclipse's platform Jars.
Ah.
I will ask a SWT comitter that told me he once managed to remove the dependency. He might be able to create a jar for me.
That won't really work unless we can patch FC's JFace build stuff to allow the JFace jar in the system to have the same dependency removed. But it's a good step forward.
Either way, I've made an SRPM and specfile available for the little hackjob I did on this:
http://www.overholt.ca/rssowl/
Things work pretty well for me. The specfile lists things that we need to do. If anyone wants to help, it'd be greatly appreciated.
Thanks,
Andrew
Andrew Overholt overholt@redhat.com wrote:
Things work pretty well for me. The specfile lists things that we need to do. If anyone wants to help, it'd be greatly appreciated.
Both blowfish-j and itext are already in JPackage. However, they are outdated, 2.12 -> 2.14 and 1.02b -> 1.3, respectively. So, JPackage has probably done most of the work already, but it would be nice to get the packages brought up to date in the process.
As for swt-nl.jar, I know green posted a message to jpackage-discuss about this jar a few months back, which he couldn't find at the time. I have found it in CVS here:
http://dev.eclipse.org/viewcvs/index.cgi/platform-swt-home/
but I don't know what it is part of (if it is not part of the swt build already).
On Tue, Jul 26, 2005 at 07:51:51AM -0400, David Walluck wrote:
Both blowfish-j and itext are already in JPackage. However, they are outdated, 2.12 -> 2.14 and 1.02b -> 1.3, respectively.
Attached is my spec for blowfish-j 2.14.
* David Walluck david@zarb.org [2005-07-26 07:52]:
Both blowfish-j and itext are already in JPackage. However, they are outdated, 2.12 -> 2.14 and 1.02b -> 1.3, respectively. So, JPackage has probably done most of the work already, but it would be nice to get the packages brought up to date in the process.
So once these are updated, we just need to get them into FE. Has anyone gone through the FE application process yet? I've been meaning to get around to it ...
As for swt-nl.jar, I know green posted a message to jpackage-discuss [...] but I don't know what it is part of (if it is not part of the swt build already).
I don't think it's part of the SWT build. I don't see the files in a build tree, either. Ben, is this necessary? I'm considering including it as a Source file in the SWT RPM - David, what do you think?
Andrew
Andrew Overholt (overholt@redhat.com):
As for swt-nl.jar, I know green posted a message to jpackage-discuss [...] but I don't know what it is part of (if it is not part of the swt build already).
I don't think it's part of the SWT build. I don't see the files in a build tree, either. Ben, is this necessary? I'm considering including it as a Source file in the SWT RPM - David, what do you think?
It's a set of translations that were contributed to eclipse from IBM. We provide them off of the SWT homepage (www.eclipse.org/swt/). Including it as a source file in the SWT RPM seems reasonable IMHO.
-Billy
Andrew Overholt overholt@redhat.com wrote:
I don't think it's part of the SWT build. I don't see the files in a build tree, either. Ben, is this necessary? I'm considering including it as a Source file in the SWT RPM - David, what do you think?
My objection is philosopical: I am always wary about shipping a binary jar that was most likely built on the non-free Sun JVM. On a more practical note, we need to find the upstream sources anyway. Can the jar be reconstructed from CVS? I am definitely for shipping these sources with eclipse/swt so that we can provide swt-nl.jar.
Hi David,
[about swt-nl.jar used by RSSOwl]
My objection is philosopical: I am always wary about shipping a binary jar that was most likely built on the non-free Sun JVM. On a more practical note, we need to find the upstream sources anyway. Can the jar be reconstructed from CVS? I am definitely for shipping these sources with eclipse/swt so that we can provide swt-nl.jar.
This jar package should contain no compiled code, be it bytecodes or native code. It should contain only message files and other resources like icons. So it's as good as a source tarball.
[]s, Fernando Lozano
* Fernando Lozano fernando@lozano.eti.br [2005-07-27 09:28]:
Can the jar be reconstructed from CVS? I am definitely for shipping these sources with eclipse/swt so that we can provide swt-nl.jar.
This jar package should contain no compiled code, be it bytecodes or native code. It should contain only message files and other resources like icons. So it's as good as a source tarball.
Yeah, I kinda feel the same way. Billy: the .properties files themselves aren't in CVS anywhere, right?
Andrew
Fernando Lozano fernando@lozano.eti.br wrote:
This jar package should contain no compiled code, be it bytecodes or native code. It should contain only message files and other resources like icons. So it's as good as a source tarball.
Sort of. I am gald to see that fc now uses tomcat5 with eclipse, but previously it used tomcat4. Even though tomcat4 code is free, it could not be built with a free compiler, so no one could reproduce it. Being able to rebuild and reproduce things, including jars even when they only contain like text files, is still important from my point of view. Otherwise, you must rely on upstream to provide you with a binary jar from some unknown location (which may or may not contain binary files within it). So the issue has to do with reproducability and reliance, not what the file necessarily contains.
Anyway, I am fairly confident this jar can be reconstructed out of the CVS URL I gave in a previous message.
David Walluck (david@zarb.org):
[...] Being able to rebuild and reproduce things, including jars even when they only contain like text files, is still important from my point of view. Otherwise, you must rely on upstream to provide you with a binary jar from some unknown location (which may or may not contain binary files within it). So the issue has to do with reproducability and reliance, not what the file necessarily contains.
A .jar isn't really any different than a .tar.gz file, both are binary blobs that contain files. This .jar is the upstream archive. It's like asking how to recreate gtk+-2.6.7.tar.gz ;) It's always important to investigate the contents of archives, but I dont think this case is really anything special beyond that.
Regardless, the CVS URL you posted earlier is the CVS repository for our homepage (www.eclipse.org/swt/) so I guess that's the upstream. I think I was incorrect earlier when I said these translations were contributed by IBM, seems that they were contributed by users for the most part.
-Billy
On Wed, 2005-07-27 at 10:52 -0500, Billy Biggs wrote:
A .jar isn't really any different than a .tar.gz file, both are binary blobs that contain files. This .jar is the upstream archive. It's like asking how to recreate gtk+-2.6.7.tar.gz ;)
tar zxf gtk+-2.6.7.tar.gz; cd gtk+-2.6.7; ./configure; make; make dist
* David Walluck david@zarb.org [2005-07-26 07:52]:
As for swt-nl.jar, I know green posted a message to jpackage-discuss
I meant to post the contents and size:
$ ls -lh swt-nl.jar -rw-rw-r-- 1 andrew andrew 9.7K Jul 27 00:32 swt-nl.jar $ unzip -l swt-nl.jar Archive: swt-nl.jar Length Date Time Name -------- ---- ---- ---- 1610 08-16-04 14:46 org/eclipse/swt/internal/SWTMessages_de.properties 1582 08-16-04 14:46 org/eclipse/swt/internal/SWTMessages_es.properties 1543 08-16-04 14:46 org/eclipse/swt/internal/SWTMessages_fr.properties 1556 08-16-04 14:46 org/eclipse/swt/internal/SWTMessages_it.properties 2424 08-16-04 14:46 org/eclipse/swt/internal/SWTMessages_ja.properties 2025 08-16-04 14:46 org/eclipse/swt/internal/SWTMessages_ko.properties 1580 08-16-04 14:46 org/eclipse/swt/internal/SWTMessages_pt_BR.properties 1907 08-16-04 14:46 org/eclipse/swt/internal/SWTMessages_zh_CN.properties 1953 08-16-04 14:46 org/eclipse/swt/internal/SWTMessages_zh_TW.properties 1944 08-16-04 14:46 about.html 0 11-26-04 09:14 org/eclipse/ 0 11-26-04 09:14 org/eclipse/swt/ 0 11-30-04 08:25 org/eclipse/swt/internal/ 0 11-26-04 09:14 org/ -------- ------- 18124 14 files
Andrew
Hi,
I updated things a bit to make the internal browser work (courtesy Robin Green in /usr/bin/eclipse) and fixed a subsequent error in the launching script. I've put my latest stuff here:
http://www.overholt.ca/rssowl/
Again, the specfile lists things that we need to do. If anyone wants to help, it'd be greatly appreciated.
Thanks,
Andrew
java-devel@lists.fedoraproject.org
-
Andrew Overholt -
Billy Biggs -
David Walluck -
Fernando Lozano -
Mark Wielaard -
Robin Green