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