[opensuse-buildservice] distro independant rpms and debs for distro independant data?
This question concerns both the OBS and packaging so I am sending to both lists. I am currently working on packaging the Swiss Ephemeris http://www.astro.com/swisseph/ I am currently at the planning scheming and experimentation stage. First I will do the library. But then there is the data. The data is about 60 files not all of which will be wanted by all people. There may be ways of grouping but I am not sure. Perhaps one rpm per file. The Web page says:
For this extended timespan the ephemeris requires 32 Mbytes of ephemeris files.
It would be a shame if this had to repeat for each distro. There may be other projects with even more data. This data is distro and architecture independent. I understand that there should be different rpm per distro because different distros link libraries differently and do other details differently. There could be rpm version dependencies. Perhaps one distro can not understand rpms from another distro as raw data. My question is this is there a lowest common denominator rpm format that can represent pure data (and a few text licensing files) and be understood by all distros? How would you get the build service to produce such rpms? After you produced them how would you get the build service to serve them for all rpm based distros? Same question for debs and the debian based distros? Unrelated question: a while back OBS debian binary repositories were debian compatible but the source repositories were not. Is this still true? -- Paul Elliott 1(512)837-1096 pelliott@BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117
On Thu, Apr 7, 2011 at 12:12 AM, Paul Elliott <pelliott@blackpatchpanel.com> wrote:
First I will do the library. But then there is the data. The data is about 60 files not all of which will be wanted by all people. There may be ways of grouping but I am not sure. Perhaps one rpm per file. The Web page says:
For this extended timespan the ephemeris requires 32 Mbytes of ephemeris files. ... My question is this is there a lowest common denominator rpm format that can represent pure data (and a few text licensing files) and be understood by all distros?
How would you get the build service to produce such rpms?
After you produced them how would you get the build service to serve them for all rpm based distros?
I have the same issue with my projects, which have ~300M of data which isn't distro-dependant. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, Apr 07, 2011 at 12:32:08AM +0200, Claudio Freire wrote:
On Thu, Apr 7, 2011 at 12:12 AM, Paul Elliott <pelliott@blackpatchpanel.com> wrote:
First I will do the library. But then there is the data. The data is about 60 files not all of which will be wanted by all people. There may be ways of grouping but I am not sure. Perhaps one rpm per file. The Web page says:
For this extended timespan the ephemeris requires 32 Mbytes of ephemeris files. ... My question is this is there a lowest common denominator rpm format that can represent pure data (and a few text licensing files) and be understood by all distros?
How would you get the build service to produce such rpms?
After you produced them how would you get the build service to serve them for all rpm based distros?
I have the same issue with my projects, which have ~300M of data which isn't distro-dependant.
Build a noarch RPM, without script usage and without special rpm requires. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello Adding BuilArch: noarch will just get him a RPM enabled for i586 and x86_64 etc, but still for the same repository. For cross-distro, what I'm personnaly doing is enabling a repository for each distro I'm interested in (Fedora_14, openSUSE_11.3, openSUSE_11.4, etc.). OBS will publish the resulting rpm in a distro-specific repo, like this for example: http://download.opensuse.org/repositories/home:/rgarrigue:/xtreemos3.0/ If that's just data, there should be no complication for your stuff to package for each distributions. Good luck, Rémy Le 07/04/2011 10:02, Marcus Meissner a écrit :
On Thu, Apr 07, 2011 at 12:32:08AM +0200, Claudio Freire wrote:
On Thu, Apr 7, 2011 at 12:12 AM, Paul Elliott <pelliott@blackpatchpanel.com> wrote:
First I will do the library. But then there is the data. The data is about 60 files not all of which will be wanted by all people. There may be ways of grouping but I am not sure. Perhaps one rpm per file. The Web page says:
For this extended timespan the ephemeris requires 32 Mbytes of ephemeris files. ... My question is this is there a lowest common denominator rpm format that can represent pure data (and a few text licensing files) and be understood by all distros?
How would you get the build service to produce such rpms?
After you produced them how would you get the build service to serve them for all rpm based distros? I have the same issue with my projects, which have ~300M of data which isn't distro-dependant. Build a noarch RPM, without script usage and without special rpm requires.
Ciao, Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
2011/4/7 Rémy Garrigue <remy.garrigue@gmail.com>:
For cross-distro, what I'm personnaly doing is enabling a repository for each distro I'm interested in (Fedora_14, openSUSE_11.3, openSUSE_11.4, etc.). OBS will publish the resulting rpm in a distro-specific repo, like this for example: http://download.opensuse.org/repositories/home:/rgarrigue:/xtreemos3.0/ If that's just data, there should be no complication for your stuff to package for each distributions.
That's the way I do it too, but it makes OBS work extra hard without need, and it also multiplies storage requirements. Not to mention a proxy's ability to cache (the proxy won't know all the rpms are equivalent). Granted, from previous responses, I think my data packages aren't entirely distribution-independent. Namely, I think I'm using a few distro-dependent macros, but that could probably be worked out. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
2011/4/7 Rémy Garrigue <remy.garrigue@gmail.com>:
Hello
Adding BuilArch: noarch will just get him a RPM enabled for i586 and x86_64 etc, but still for the same repository.
Bumping a really old thread here, but again I'm noticing some inefficiency in OBS. If both x86_64 and i586 are enabled for a noarch package, it's built twice, but only one rpm is created. Question: is it safe for me to disable one of the archs and thus save some redundant work for OBS? (I imagine it is) Question: wouldn't it be great if OBS did that "optimization" automatically? (after all, if only one RPM is published, what's the point of building twice?)
For cross-distro, what I'm personnaly doing is enabling a repository for each distro I'm interested in (Fedora_14, openSUSE_11.3, openSUSE_11.4, etc.). OBS will publish the resulting rpm in a distro-specific repo, like this for example: http://download.opensuse.org/repositories/home:/rgarrigue:/xtreemos3.0/ If that's just data, there should be no complication for your stuff to package for each distributions.
Good luck, Rémy
Le 07/04/2011 10:02, Marcus Meissner a écrit :
On Thu, Apr 07, 2011 at 12:32:08AM +0200, Claudio Freire wrote:
On Thu, Apr 7, 2011 at 12:12 AM, Paul Elliott <pelliott@blackpatchpanel.com> wrote:
First I will do the library. But then there is the data. The data is about 60 files not all of which will be wanted by all people. There may be ways of grouping but I am not sure. Perhaps one rpm per file. The Web page says:
For this extended timespan the ephemeris requires 32 Mbytes of ephemeris files.
... My question is this is there a lowest common denominator rpm format that can represent pure data (and a few text licensing files) and be understood by all distros?
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mon, Jan 30, Claudio Freire wrote:
Bumping a really old thread here, but again I'm noticing some inefficiency in OBS. If both x86_64 and i586 are enabled for a noarch package, it's built twice, but only one rpm is created.
Good point. Especially when just building noarch packages.
Question: is it safe for me to disable one of the archs and thus save some redundant work for OBS? (I imagine it is)
I am doing that since quite some time now, but I am just building noarch packages.
Question: wouldn't it be great if OBS did that "optimization" automatically? (after all, if only one RPM is published, what's the point of building twice?)
+1 -- With best regards, Carsten Hoeger
On 1/31/2012 2:14 AM, Carsten Hoeger wrote:
On Mon, Jan 30, Claudio Freire wrote:
Bumping a really old thread here, but again I'm noticing some inefficiency in OBS. If both x86_64 and i586 are enabled for a noarch package, it's built twice, but only one rpm is created.
Good point. Especially when just building noarch packages.
Question: is it safe for me to disable one of the archs and thus save some redundant work for OBS? (I imagine it is)
I am doing that since quite some time now, but I am just building noarch packages.
Question: wouldn't it be great if OBS did that "optimization" automatically? (after all, if only one RPM is published, what's the point of building twice?)
+1
It at least verifies that the build process works on both arches. -- bkw -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Dienstag, 31. Januar 2012, 08:14:50 schrieb Carsten Hoeger:
On Mon, Jan 30, Claudio Freire wrote:
Bumping a really old thread here, but again I'm noticing some inefficiency in OBS. If both x86_64 and i586 are enabled for a noarch package, it's built twice, but only one rpm is created.
Good point. Especially when just building noarch packages.
Question: is it safe for me to disable one of the archs and thus save some redundant work for OBS? (I imagine it is)
I am doing that since quite some time now, but I am just building noarch packages.
It is only safe, when you do not use the noarch package again as build requires. Otherwise you will have unresolvables.
Question: wouldn't it be great if OBS did that "optimization" automatically? (after all, if only one RPM is published, what's the point of building twice?)
it is not that easy when you take boot strapping and build cycles into account. One arch would need to inject the package into the other archs and build cycles can be detected that easily anymore. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (7)
-
Adrian Schröter -
Brian K. White -
Carsten Hoeger -
Claudio Freire -
Marcus Meissner -
Paul Elliott -
Rémy Garrigue