On May 29, 2013, at 10:40 PM, "T.C. Hollingsworth" <[email protected]> wrote:
> On Wed, May 29, 2013 at 6:55 PM, T.C. Hollingsworth > <[email protected]> wrote: >> Any ideas about what we could do here? Or should I elevate this to >> [email protected] for wider input? > > I went ahead and did just that: > https://lists.fedoraproject.org/pipermail/epel-devel/2013-May/008482.html > This should probably go to FPC, rather than devel. 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. 2) On EPEL6, build all nodejs- packages as archful instead of noarch. 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. >> The good news is this works great for binary modules, both locally >> here on F19 and on Rawhide in koji: >> http://koji.fedoraproject.org/koji/taskinfo?taskID=5440548 > > As an addendum to this, this also works as expected on architectures > where packages *shouldn't* build: > http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=1136458 > > -T.C. > _______________________________________________ > nodejs mailing list > [email protected] > https://admin.fedoraproject.org/mailman/listinfo/nodejs _______________________________________________ nodejs mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/nodejs
