Bug#882445: Proposed change of offensive packages to -offensive

2017-11-23 Thread Sean Whitton
Hello David, On Thu, Nov 23 2017, David Kalnischkies wrote: > On Wed, Nov 22, 2017 at 05:18:37PM -0700, Sean Whitton wrote: >> > "cowsay-offensive". In this situation the "-offensive" package can >> > be Suggested by the core package(s), but should not be Recommended >> > or Depended on, s

Bug#882445: Proposed change of offensive packages to -offensive [and 1 more messages]

2017-11-23 Thread Ian Jackson
David Kalnischkies writes ("Re: Bug#882445: Proposed change of offensive packages to -offensive"): > On Wed, Nov 22, 2017 at 05:18:37PM -0700, Sean Whitton wrote: > > > "cowsay-offensive". In this situation the "-offensive" package can > > > be Suggested by the core package(s), but should not

Bug#882445: Proposed change of offensive packages to -offensive

2017-11-23 Thread David Kalnischkies
On Wed, Nov 22, 2017 at 05:18:37PM -0700, Sean Whitton wrote: > > "cowsay-offensive". In this situation the "-offensive" package can > > be Suggested by the core package(s), but should not be Recommended > > or Depended on, so that it is not installed by default. ^^

Bug#882445: Proposed change of offensive packages to -offensive

2017-11-23 Thread Iain R. Learmonth
Hi, On 23/11/17 00:18, Sean Whitton wrote: >> So to be concrete, how about this: >> >> N. Packages with potentially offensive content >> >> As a maintainer you should make a judgement about whether the >> contents of a package is appropriate to include, whether it needs >> any kind of cont

Bug#882445: possible offensive packages in suggest

2017-11-23 Thread Geert Stappers
> > If you split out (potentially) offensive or disturbing material into > a separate package, you should usually mark this in the package name > by adding "-offensive". For example, "cowsay" vs > "cowsay-offensive". In this situation the "-offensive" package can > be Suggested by the core packag