Make ppc64 secondary arch - don't block builds (was: Dealing with ppc64 BRs)

[Axel Thimm]

On Mon, Aug 06, 2007 at 08:11:08AM -0500, Josh Boyer wrote:
> On Mon, 6 Aug 2007 15:01:44 +0200
> Axel Thimm <Axel.Thimm at ATrpms.net> wrote:
> 
> > On Mon, Aug 06, 2007 at 07:58:50AM -0500, Dennis Gilmore wrote:
> > > Once upon a time Monday 06 August 2007, Axel Thimm wrote:
> > > > Hi,
> > > >
> > > > when ppc64 is missing some BRs the builds fail. I feel like it's
> > > > overshooting to start having ExclusiveArchs/ExlcudeArchs, but maybe
> > > > that's the way one needs to go with modern build systems ... :/
> > > >
> > > > More concrete mediawiki BR-depends on ocaml and that seems not to
> > > > exist on ppc64 booming all builds. What's the proper way to fix this?
> > > 
> > > Get what you need built fpr ppc64.
> > 
> > ?
> > 
> > Should I volunteer to maintain package foo and bar on ppc64 becasue
> > they are BRs to my baz?
> 
> David was working on ocaml at one point.  For now, ExcludeArch it and
> file the appropriate ExcludeArch bug.  When ocaml is built, you can
> remove it and rebuild.

Ugly - we need to artificially bump the release to exclude it and
later bump to undo the ugliness. In the meantime we enforce users to
download this twice (or trice) and not only for the affected distros,
as fiddling with release tags has a domino effect to later releases
(not that it matters in this case, devel is missing ocaml.ppc64 just
the same).

And all that for archs that are already scheduled to become secondary
archs, e.g. not block builds? ppc/ppc64 were supposed to become
secondary archs if another arch was to be found to be secondary and we
already have arm for filling that requirement, so since it's already a
closed deal, why do we need to go through this pain?

And shouldn't ppc64 (or any half-built arch) had been automatically
introduced as a secondary arch anyway to not mess with normal
packaging workflow? Even if the intention were to elevate it later to
a primary arch someday? What will happen with the next arch that will
be added? Have all packages ExcludeArch it to start with?
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-maintainers/attachments/20070806/e4bb014b/attachment.sig>