On Fri, May 3, 2013 at 6:53 AM, T.C. Hollingsworth
<tchollingsworth(a)gmail.com> wrote:
> Please remember to consider the bootstrapping problem in the
event of
> future mass-rebuilds. If the nodejs package starts build-depending on
> the npm package, that's a circular dependency that becomes very
> difficult to maintain. (I've seen how they have to do it in GCC, and
> it's not pretty).
I'm just talking about Requires: npm. We definitely wouldn't need
BuildRequires on it (the only way that would ever be possible is for
%check, but there's no network in koji so we couldn't use it for any
tests there anyway). So, this shouldn't be a problem?
Actually, come to think of it, there's still a nasty dep loop if
npm2rpm and nodejs-packaging share SRPMs regardless of whether its
build-time or runtime. It don't think it's realistically a problem
for Fedora secondary arches since they just import noarch binary RPMs
from primary wholesale, but better to avoid it anyway.
I'll get a nodejs-packaging package up for review soonish, so we can
hopefully migrate to it when 0.10.6 comes out (which ought not to be
for a little while; I see no interesting commits on the v0.10 branch
since 0.10.5).
-T.C.