[opensuse-packaging] 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
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-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+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
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-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
2011/4/7 Marcus Meissner
On Thu, Apr 07, 2011 at 12:32:08AM +0200, Claudio Freire wrote:
On Thu, Apr 7, 2011 at 12:12 AM, Paul Elliott
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.
It would still be nice to be able to create a *single* "noarch-nodistro" RPM and symlink it in every distro-specific repo. Mirrors would appreciate it. And the build service can also take some time to build these packages since they can require quite some IO. Not trying to say it's so simple. A distro could not support the XZ compression or some other RPM feature. But would be nice... -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Thu, Apr 7, 2011 at 10:02 AM, Marcus Meissner
On Thu, Apr 07, 2011 at 12:32:08AM +0200, Claudio Freire wrote:
On Thu, Apr 7, 2011 at 12:12 AM, Paul Elliott
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.
And without "distro" specific macro, without using rpm functionality not upstream (not so simple for the average packager), .... BTW, something very related was discussed some years ago http://www.mail-archive.com/rpm-maint@lists.rpm.org/msg00939.html but probably not really of distro interest, more interested in something like branding and the like. JMHO Ciao Elia -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (5)
-
Claudio Freire
-
Cristian Morales Vega
-
Marcus Meissner
-
Paul Elliott
-
yersinia