Hi,
I'm trying to package Bluecove (a Java stack implementation of JSR-82) using BlueZ [1].
Upstream has two tars: (bluecove-2.1.0-source.tar.gz) which contains everything needed for platforms like Windows and OS X (Apache 2 license), and for Linux a separate tar (bluecove-gpl-2.1.0-sources.tar.gz) that contains some BlueZ JNI foo (and which is GPL licensed).
Does it make sense to put this all in one spec file/package? Bluecove without the "gpl" part is useless on Linux.
It would probably be cleanest to just have one spec file and one package that includes the jar file and the native library? But this would require fiddling with Source0 and Source1 and some setup macros. Are there any examples of this? Any advice?
Thanks, François
Hi,
François Kooman wrote:
I'm trying to package Bluecove (a Java stack implementation of JSR-82) using BlueZ [1].
Cool.
Does it make sense to put this all in one spec file/package? Bluecove without the "gpl" part is useless on Linux.
Sure.
But this would require fiddling with Source0 and Source1 and some setup macros. Are there any examples of this? Any advice?
The Eclipse SDK spec -- eclipse.spec -- is huge and overkill for what you're looking for but it has multiple sources. OTTOMH I can't think of other examples. Anyone else?
Andrew
Andrew Overholt wrote:
Hi,
François Kooman wrote:
I'm trying to package Bluecove (a Java stack implementation of JSR-82) using BlueZ [1].
Cool.
Does it make sense to put this all in one spec file/package? Bluecove without the "gpl" part is useless on Linux.
Sure.
But this would require fiddling with Source0 and Source1 and some setup macros. Are there any examples of this? Any advice?
The Eclipse SDK spec -- eclipse.spec -- is huge and overkill for what you're looking for but it has multiple sources. OTTOMH I can't think of other examples. Anyone else?
dovecot has multiple sources and the spec includes 3 invocations of %setup.
Paul.
Andrew Overholt wrote:
The Eclipse SDK spec -- eclipse.spec -- is huge and overkill for what you're looking for but it has multiple sources. OTTOMH I can't think of other examples. Anyone else?
I looked at that and also some RPM resources online (and dovecot SPEC). In the end I came up with:
%setup -q %setup -q -T -D -a 1
Which unpacks Source0 (quietly) and after that unpacks Source1 inside the extracted Source0, without deleting the parent (Source0) directory.
This seems to work, I have a preliminary SPEC file at http://users.tuxed.net/fkooman/rpmbuild/SPECS/bluecove.spec in case anyone is interested, but it is not quite ready for review yet.
Thanks, François
On Thu, Jan 15, 2009 at 11:14:08AM +0100, François Kooman wrote:
I looked at that and also some RPM resources online (and dovecot SPEC). In the end I came up with:
%setup -q %setup -q -T -D -a 1
Looks good to me. That's what I do in cernlib, too (but you don't want to look a the spec file for an example...).
-- Pat
On Thu, 2009-01-15 at 11:14 +0100, François Kooman wrote:
%setup -q %setup -q -T -D -a 1
Which unpacks Source0 (quietly) and after that unpacks Source1 inside the extracted Source0, without deleting the parent (Source0) directory.
This should be equivalent to:
%setup -q -a 1
packaging@lists.fedoraproject.org
-
Andrew Overholt -
François Kooman -
Ignacio Vazquez-Abrams -
Patrice Dumas -
Paul Howarth