On 07/14/2017 12:57 PM, Tollef Fog Heen wrote:
Fair point.
3. Once a new nodejs package providing /usr/bin/node is in the
archive, other packages in the archive are free to depend on the
nodejs package and use /usr/bin/node .
That should probably be a versioned Depends, at least
Someone asked for an example, here is one I've often seen when doing a
release upgrade on many webservers I administer: Apache will fail to
start. I don't recall if that currently causes Apache postinst to fail,
but if not, it really ought to continue.
Apache has a complicated config, and upst
It's different than awk because the decision the admin is making ("which
init system do I want to run"?) isn't done through alternatives. So you
can't use the alternatives system to coordinate swapping all the
different bits together.
It seems retty reasonable to me that the systemd maintainer
On 1/29/20 2:19 PM, Simon McVittie wrote:
I think we have a fairly good picture of the costs that would be
incurred from using alternatives: more interacting code paths to test,
potentially more configurations that are technically possible but are
not considered supported, and packages with "Depe
On 1/30/20 7:02 AM, Thomas Goirand wrote:
This is normally solved if using pre-depends, which ensure that a
package is configured before using it (and not just unpacked).
Having everything using sysusers have versioned Pre-Depends on systemd |
opensysusers would probably minimize the problem,
5 matches
Mail list logo
