Hi![...]
* libaudit-dev[...]
- Rationale:
This could allow to add Linux audit support to dpkg on package action
events. I've got a branch that might need minor polishing, but could
otherwise be merged.
- Essential/Build-Essential:
On Linux it is already part of the pseudo-essential set.
* libcap-dev[...]
- Rationale:
This could allow to add support to start-stop-daemon (already code
available) to drop POSIX capabilities. And also in the future (either
later in 1.21.x or 1.22.x) to support fsys POSIX capabilities as part
of the fyss metadata tracking support that is upcoming.
- Essential/Build-Essential:
On Linux it is already part of the pseudo-essential set.
On Wed, Jul 06, 2022 at 05:13:05AM +0200, Guillem Jover wrote:
[...]
* libaudit-dev
- Rationale:
This could allow to add Linux audit support to dpkg on package action
events. I've got a branch that might need minor polishing, but could
otherwise be merged.
- Essential/Build-Essential:[...]
On Linux it is already part of the pseudo-essential set.
* libcap-dev
- Rationale:
This could allow to add support to start-stop-daemon (already code
available) to drop POSIX capabilities. And also in the future (either
later in 1.21.x or 1.22.x) to support fsys POSIX capabilities as part
of the fyss metadata tracking support that is upcoming.
- Essential/Build-Essential:[...]
On Linux it is already part of the pseudo-essential set.
IIRC there are several competing capability libraries already part of
pseudo essential. I think it would be good if we could identify one and
work towards having only that in pseudo essential (and in theory maybe
the entire archive use it). Maybe it's out of scope for this discussion though...
Unless I'm mistaken if dpkg dep on libcap(2) and libaudit, then dpkg
would transitively dep on both libcap(2) and libcap-ng which seems suboptimal.
Unless I'm mistaken if dpkg dep on libcap(2) and libaudit, then dpkg
would transitively dep on both libcap(2) and libcap-ng which seems suboptimal.
Yes, but its an internal implementation detail, so libaudit could be switched, and for now, at least they will not end up in the same address space. Of course pulling both is not ideal, but on Linux they are both already part of the pseudo-essential set anyway, and they are tiny
compared to say the libzstd one, so…
As per Debian policy §3.5, and given dpkg “Essential: yes” nature, I'm bringing up the following potential additions to dpkg's Pre-Depends,
and whether there is consensus about each of them individually and independently.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 33:22:40 |
Calls: | 6,707 |
Files: | 12,239 |
Messages: | 5,353,262 |