2011/4/7 Rémy Garrigue email@example.com:
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 firstname.lastname@example.org 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?