C++ Logo


Advanced search

Re: Defining Roles of Tools in Dependency Management

From: Ran Regev <regev.ran_at_[hidden]>
Date: Tue, 19 Mar 2024 23:15:43 +0900
On Tue, Mar 19, 2024, 21:35 Boris Kolpackov via SG15 <sg15_at_[hidden]>

> Bret Brown via SG15 <sg15_at_[hidden]> writes:
> > - One is a dependency manager (a.k.a. package manager)
> > - These resolve dependencies on source or binary artifacts
> > - The second role is a build system
> > - These construct and order build commands
> > - The third role... needs name
> > - This takes the universe populated by the dependency manager and
> > flattens a projection into the specific view needed by the build
> > system to construct a target model (i.e., model libraries and
> > executables)
> One things that immediately strikes me as problematic in this model
> are conditional dependencies that are often based on information that
> is only known by the build system (target platform, compiler, compiler
> version, stdlib used, etc). Which means that there is a feedback loop
> from the build system to the package manager. You could probably make
> the user supply this information to the package manager manually, but
> that won't scale beyond basic things.

I am OK with back and forth flow of data, as long as it clears who is
responsible to what.

So id there is a need to query the package manager before requesting it for
more information based on the answer, it is ok.

> .
> _______________________________________________
> SG15 mailing list
> SG15_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg15

Received on 2024-03-19 14:15:57