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