First the actual issue of this bug may be solved because we have found
a technical solution by cheating a little bit on dependencies:
Second ATM in debian node-babel-preset-env is separate from node-babel,
but upstream moved it back into the main babel repo:
"Now that babel-preset-env has stabilized, it has been moved into the main Babel
So in the near future node-babel-preset-env may well be one of the binaries
generated from node-babel source. And when that happens, babel will depend on
Third considering the ephemeral nature of the boundaries between one package and
another, I propose that we consider circular references in general, be them
a package or across packages.
Fourth to Don, many thanks for trying to find a clean technical solution, but
won't work in this case because the babel makefile bootstrap target does:
cd packages/babel-runtime; node scripts/build-dist.js
and yarn and lerna are both WIP:
- yarn: https://bugs.debian.org/843021
- lerna: https://bugs.debian.org/849258
and both depend on babel:
so it's still a circular reference !
Now back to the issue, while it is certainly possible to bootstrap gcc,
babel, rollup or any self-compiling compiler, how much skills and time it
requires to achieve it once AND to keep it working when upstream moves on
varies a lot.
The bootstrap process of gcc for example is stable and supported by
upstream. Once you have that, there is still a lot of work to set it up in
debian, but if it works it is likely to keep working in the future.
not in the business of systems programming and does not care about a clean,
"orthodox" bootstrap, it can be harder to get once and even harder to keep
working when upstream changes tooling, language versions ...
enthusiasms of upstream. The whole point of making debian or derivatives
some may volunteer and channel some of their enthusiasm in integrating
In conclusion I think it would be nice to be able to close this bug keeping
in mind that we need to be a bit flexible with all this node-* stuff !