On Thu, May 30, 2013 at 2:52 AM, Stephen Gallagher <sgallagh(a)redhat.com> wrote:
This should probably go to FPC, rather than devel.
I intended that as a slightly more polite way of asking dgilmore
and/or nirik for their input, since this is kind of a rel-eng issue.
I can immediately think of two solutions to this, but I do not like
either of them:
1) Ask rel-eng to simply block the inclusion on any package starting with nodejs- from
being shipped in repos for the unsupported arches.
I have a feeling that blocking nodejs-* in koji sounds simple enough
to us but would be a nightmare for our already overworked rel-eng
folks. It doesn't look like koji's blocking mechanism  supports
2) On EPEL6, build all nodejs- packages as archful instead of noarch.
What about 3.) Just hack something into the script that sends out
dependency warning e-mails to ignore nodejs-* (or much more preferably
the output of `repoquery --whatrequires nodejs`).
That wouldn't fix the issue of metadata bloat on PPC (or having a
bunch of useless RPMs in the PPC repo, but we hardlink everything so
that shouldn't matter), but it would at least make dependency warnings
in EPEL useful again. Option 2 is slightly more clean, but if we go
that route instead of slightly larger metadata on PPC we just double
the number of RPMs on the mirrors.
So it seems the question we're asking is—whose lives do we want to
make more miserable: Kevin and Dennis', mirror admins', or PPC users'
waiting for yum to download metadata. :-P
(Speaking of making lives miserable, I might add that my option 3 only
requires me to write one patch, while option 2 involves scripting
patches for ~200 packages, which makes it appeal even more to me. ;-)
Question: how does PERL handle this in EPEL? I know there are PERL
packages that can only be shipped for certain arches because they exist in core RHEL for a
subset of the supported arches.
<wild guess> Wouldn't those would be archful anyway, and not affected
by this? (Even if they weren't archful to begin with, I suspect
making them archful would be the answer to this question?) </wild