On Sat, Nov 12, 2022 at 09:30:43PM +0100, Guillem Jover wrote:

> There was a bug filed requesting adding custom output format support
> (#214566) but it was closed “recently”. I think there might be some
> value in that, but not for the intended use the submitters seemed
> to want it.
> 
> I'd be interested to know how you'd want to use this new output/option
> as from the PoC script you provide it is not obvious to me, as it
> prints both build-depends and build-conflicts in an indistinguishable
> way, and it includes version constraints and alternative dependencies.

My specific use case at the moment is setting up a container
*description* (not a container) with all the dependencies I need to do
development on a package[1].

I could run apt-get build-dep inside the container and get the
development environment installed, but then I lose the ability of being
able to describe it in a terse way, and I can only do something along
the lines of listing all installed packages in the container and their
versions, which is too noisy for an average bug report.

The way I chopped dpkg-checkbuilddeps was a first approximation. Given
that now we have `apt-get satisfy`, my next step would be to have my
hacked version print a list of arguments for it, which can include
"Conflicts:", but which can already be preprocessed to reduce some noise
like packages required or not required from the target architecture.

More generally, I'd like Debian to have, as a standard, something
similar to `rpmspec --parse filename.spec | grep BuildRequires`
because I see it reimplemented so many times (pbuilder, sbuild, and so
on) that my instincts screams invoking the rule of three and
refactor[2].


Enrico

[1] some background context can be found in
    https://github.com/ARPA-SIMC/moncic-ci/issues/74
    although I'm expanding on that, see for example
    https://github.com/ARPA-SIMC/moncic-ci/issues/77
[2] https://en.wikipedia.org/wiki/Rule_of_three_(computer_programming)
-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini <enr...@enricozini.org>

Attachment: signature.asc
Description: PGP signature

Reply via email to