On Sun, Feb 02, 2020 at 01:31:14AM +0100, Bill Allombert wrote:
> On Sat, Feb 01, 2020 at 11:59:34AM -0800, Russ Allbery wrote:
> > I've never liked the rule that you don't have to declare dependencies on
> > essential packages and would love to phase it out as much as possible (I
> > think even in
On Sat, Feb 01, 2020 at 11:59:34AM -0800, Russ Allbery wrote:
> I've never liked the rule that you don't have to declare dependencies on
> essential packages and would love to phase it out as much as possible (I
> think even intermediate movement in that direction would be useful), but
> I'd like G
Russ Allbery wrote:
> I think Josh is arguing that ideally we'd slowly move towards declaring
> dependencies on essential packages explicitly, so we should indicate that
> in Policy and, as a first step, say that we're not adding any entirely new
> functionality to the essential set if we can help
Ansgar writes:
> Is the current wording in Policy not sufficient? In 3.8 Essential
> packages it states "this flag must not be used unless absolutely
> necessary" and later "You must not tag any packages essential before
> this has been discussed on the debian-devel mailing list and a consensus
Package: debian-policy
Version: 4.5.0.0
Severity: normal
Hi!
This was brought up on debian-devel, and I think it needs to be
updated/corrected in the policy manual:
On Fri, 2020-01-17 at 12:21:11 +0100, Guillem Jover wrote:
> On Fri, 2020-01-17 at 11:12:50 +0100, Ansgar wrote:
> > Johannes Schau
5 matches
Mail list logo
