* Niels Thykier <[email protected]> [260618 08:45]:
I was updating a chroot, and I got systemd pulled in automatically due
to the dh_installtmpfiles misc:Depends values.
[..]
Those who cannot remember the past are condemned to repeat it. And I
forgot #1017441 - that is on me.
[..]
But even then, I think the main problem here is that we are trying to
express different defaults for different cases via the dependency
system. The dependency system is not built for that, so no matter what
I do, the order will be wrong for some case.
[..]
I think in the past it was always concluded that the orders and
defaults that get expressed in packages and control files are for
the "default installation" (whatever that is, but supposedly a
single user unix machine possibly with a graphical desktop), and
everyone else has to make local adjustments.
I don't like this, but that seems to be the general consensus.
Ideally we could tell installation-like tools what the intended
usecase of the Debian installation is, but outside of d-i I'm not
aware of anything there. Ideally this approach could be shared
between different tools, so not each and every tool has to reinvent
the wheel.
Maybe some metapackages would be a first step. They could pick/force
the tmpfiles and sysusers providers.
Chris
