Good morning Jan
On Mon, 20 Sept 2021 at 12:40, Jan Bölsche <jan@xxxxxxxxxxxx> wrote:
The mpc package is the multiprecision floating point libraryHa, that make so much more sense! Sorry for the confusion.
Got it! Needed packages to build a package are the ones explicitly listed
in build.textproto plus the dependencies of the referenced builder. It
might be helpful, on a fresh system, to have this list available for
scripting. A subcommand like `distri list-build-dependencies` or `distri
ls-build-deps` that basically outputs the result of
could be used as a building block for boot-strapping a working build
environment. What do you think?
Well, `distri batch` builds multiple packages in correct order, therebyfulfilling all dependencies.
The only downside is that it might attempt to build much more than youare looking for, depending on what’s in your $DISTRIROOT/_build.
If you clone the entire mirror, it shouldn’t build anything, and if youthen change something, it should build all that’s necessary.
That is very useful. `distri batch` also relies on the builder's deps to
already be installed, right?
A simpler alternative to the proposed subcommand above could be `distri
builder-deps`, that just outputs the union of all builder's dependencies.
So you could bootstrap a dev environment like so:
`distri install $(distri builder-deps)`
I think that would be even nicer than simply having all build tools