Efficient organization of project

English Open Build Service (OBS)
#1

Hi,

I’m building a lot of python packages. As I already learned, the package contains byte code, so it makes sense to build it as ‘noarch’.
That basically means, the packages for SLE, openSUSE 13.1, 13.2, Factory, Tumbleweed, x86 and x86_64 are identical.

Am I right?

If so, it does not make sense to build against each target, if the result is the same anyway.
Is there a more efficient way how I can organize my project to have only one build, but the package available for the other architectures / targets as well?

Thanks!

#2

On Fri 29 May 2015 02:36:01 PM CDT, DocB wrote:

Hi,

I’m building a lot of python packages. As I already learned, the package
contains byte code, so it makes sense to build it as ‘noarch’.
That basically means, the packages for SLE, openSUSE 13.1, 13.2,
Factory, Tumbleweed, x86 and x86_64 are identical.

Am I right?

If so, it does not make sense to build against each target, if the
result is the same anyway.
Is there a more efficient way how I can organize my project to have only
one build, but the package available for the other architectures /
targets as well?

Thanks!

Hi
Which versions of SLE?

Have a look here and add the required bits in your spec file, see
“Compatibility with older distributions”;
https://en.opensuse.org/openSUSE:Packaging_Python

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

#3

SLE-12

Have a look here and add the required bits in your spec file, see
“Compatibility with older distributions”;
https://en.opensuse.org/openSUSE:Packaging_Python

Yes, I know this page.https://en.opensuse.org/openSUSE:Packaging_Python#System_Architecture describes the noarch setup.
But it does not answer the question about project organization…

#4

On Fri 29 May 2015 03:36:02 PM CDT, DocB wrote:

malcolmlewis;2712641 Wrote:
> Hi
> Which versions of SLE?
>
SLE-12
>
> Have a look here and add the required bits in your spec file, see
> “Compatibility with older distributions”;
> https://en.opensuse.org/openSUSE:Packaging_Python
>
Yes, I know this page.’
https://en.opensuse.org/openSUSE:Packaging_Python#System_Architecture’
(https://en.opensuse.org/openSUSE:Packaging_Python#System_Architecture)
describes the noarch setup.
But it does not answer the question about project organization…

Hi
Just build one arch if they are noarch for each release, eg x86_64,
since it’s SLE 12, then you can ignore the macros.

You need to build against the release since they may use different tool
chains.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

#5

OK, so no synergies between the different releases…but then there is no point it making it noarch…

#6

Hi
It depends on what supporting packages are required which maybe arch/release specific. At present there is some commonality between SLE 12 and 13.2, easier to build a noarch per release.