Hi Helmut,
* Helmut Grohne <hel...@subdivi.de> [210824 10:10]:
> On Mon, Aug 23, 2021 at 03:33:04PM +0000, Debian Bug Tracking System wrote:
> > 2.35.2-7 disabled the cryptsetup bits. In 2.37.2-2 we will have a
> > !stage1 and dlopen-enabled version of the code.
>
> This sounds good except for the use of stage1. We've deprecated the
> profile name stage1, because it doesn't tell what it does. Please use a
> functional profile name instead. Most likely, you'll need something
> matching pkg.cryptsetup.*.
Thanks for the info, however I would not know what to use.
util-linux has a lot of !stage1 Build-Depends today:
bc <!stage1 !nocheck>,
libaudit-dev [linux-any] <!stage1>,
libcap-ng-dev [linux-any] <!stage1>,
libcryptsetup-dev [linux-any] <!stage1>,
libpam0g-dev <!stage1>,
libsystemd-dev [linux-any] <!stage1>,
libudev-dev [linux-any] <!stage1>,
netbase <!stage1 !nocheck>,
socat <!stage1 !nocheck>,
systemd [linux-any] <!stage1>,
And also !stage1 excludes most of the util-linux binary packages,
except for lib* and lib*-dev. I imagine this was done to allow
building some reverse-dependencies.
Given this it would "feel" more like a pkg.util-linux.justlibs
profile...
Is there an overview of the currently in use values in the extension
namespace?
Chris
