Hi,
Quoting Jérémy Bobbio (2016-02-04 12:23:05)
> We have to educate them about .buildinfo file and what the various fields
> mean. We have to aim at field names that are as unambigious as possible to
> avoid laying traps on users.
>
> For the particular case of “Installed-Transitive-Build-Depend
Holger Levsen:
> I know that *you* have grasped the concept of transitive build depends very
> well, but I'm pretty sure that 97% of the DD population have no idea what
> transitive build depends are, especially compared to build-depends or
> alternative build-depends. And even 70% were too many
Hi Josch,
On Donnerstag, 4. Februar 2016, Johannes Schauer wrote:
> > (AFAIK transitive build-depends are all possible build depends,
> no, that would be the build dependency closure ;)
and
> > so if a package build depends on python2 || python3 both python versions
> > will be part of the tra
Hi,
Quoting Holger Levsen (2016-02-04 11:31:32)
> (AFAIK transitive build-depends are all possible build depends,
no, that would be the build dependency closure ;)
> so if a package build depends on python2 || python3 both python versions will
> be part of the transitive build depends. (Is that
Hi Josch,
On Donnerstag, 4. Februar 2016, Johannes Schauer wrote:
> maybe we can merge Lunar's original suggestion Installed-Build-Depends (a
> name which is missing the transitive/recursive-ness) with the new
> suggestion and make it:
>
> Installed-Transitive-Build-Depends
>
> This way it would