Mailinglist Archive: opensuse-packaging (235 mails)
| < Previous | Next > |
Re: [opensuse-packaging] Cannot submit a noarch package
- From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
- Date: Fri, 30 Mar 2012 13:33:10 -0400
- Message-id: <CAGpXXZJOM8EennDLH+QftJLbSn+ZBrzD4TeFw5VM_Eb_KQ2gbw@mail.gmail.com>
On Fri, Mar 30, 2012 at 12:52 PM, Claudio Freire <klaussfreire@xxxxxxxxx> wrote:
Claudio,
I think that is the easy part. I can think of of at least 3 ways:
1) Allow noarch builds of just one arch to be accepted to factory.
Then encourage people to just enable one arch. Hopefully randomly to
spread the load around.
2) Create a new "noarch" architecture and scheduler. Have that feed
whatever actual scheduler has the lightest load at schedule time.
That way even non-Intel machines could build the noarch packages.
3) Enforce in all schedulers but one, that they ignore noarch
packages. Then document that so everyone knows they can only build
noarch on i586 (as an example).
idea 1) seems relatively doable for a modest effort.
idea 2) would require changes lots of places I assume, so it is not trivial.
idea 3) seems like the least work by far, and it sheds work load from
one of the schedulers. I don't know if that would benefit the overall
OBS load or not.
And I'm sure there are other ways.
===
The question is if the wasted build resources is worth the R&D to
bother with fixing this.
Greg
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx
On Fri, Mar 30, 2012 at 1:46 PM, Greg Freemyer <greg.freemyer@xxxxxxxxx>
wrote:
It obviously wastes cpu cycles building it twice. If you want to
change that make a proposal, but realize it is a change.
It's not easy either from what I've been told since schedulers for
i586 and x86_64 don't know about each other.
Claudio,
I think that is the easy part. I can think of of at least 3 ways:
1) Allow noarch builds of just one arch to be accepted to factory.
Then encourage people to just enable one arch. Hopefully randomly to
spread the load around.
2) Create a new "noarch" architecture and scheduler. Have that feed
whatever actual scheduler has the lightest load at schedule time.
That way even non-Intel machines could build the noarch packages.
3) Enforce in all schedulers but one, that they ignore noarch
packages. Then document that so everyone knows they can only build
noarch on i586 (as an example).
idea 1) seems relatively doable for a modest effort.
idea 2) would require changes lots of places I assume, so it is not trivial.
idea 3) seems like the least work by far, and it sheds work load from
one of the schedulers. I don't know if that would benefit the overall
OBS load or not.
And I'm sure there are other ways.
===
The question is if the wasted build resources is worth the R&D to
bother with fixing this.
Greg
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx
| < Previous | Next > |