On Tue, Dec 13, 2022 at 10:14:55AM -0800, Vagrant Cascadian wrote:
> On 2022-12-13, James Addison via rb-general wrote:
> > As Debian's buildinfo[1] wiki page hints, it's difficult to determine
> > whether a build dependency is genuinely required at build-time,
> > compared to: it was required in
Ah, typical: while trying to figure out where functionality like this
could fit into Debian, I learned that it already exists there.
The 'dpkg-depcheck' and 'dpkg-genbuilddeps' utilities (both included
in the 'devscripts' package) provide this kind of functionality in
Debian.
On Wed, 14 Dec 2022
On Tue, 13 Dec 2022 at 18:15, Vagrant Cascadian
wrote:
>
> It would be interesting to do something more systematic like your
> suggestion, though I'm not aware of anything at the moment.
Thanks Vagrant, that's good to know (it matches my understanding too,
from searching around).
Roughly
On 2022-12-13, James Addison via rb-general wrote:
> As Debian's buildinfo[1] wiki page hints, it's difficult to determine
> whether a build dependency is genuinely required at build-time,
> compared to: it was required in the past, but has become dependency
> cruft.
>
> I was wondering: are there
Hi folks,
As Debian's buildinfo[1] wiki page hints, it's difficult to determine
whether a build dependency is genuinely required at build-time,
compared to: it was required in the past, but has become dependency
cruft.
I was wondering: are there reproducible-builds efforts underway (in
Debian or
