Hi, On 6/5/20 1:34 PM, Ansgar wrote: > On Fri, 2020-06-05 at 12:09 +0200, Hans van Kranenburg wrote: >>> Installing NEWS into xen*, but not libxen* probably still reaches all >>> relevant users. >> >> Yes, that makes sense. >> >> OTOH, what if there was a really weird problem with libxenmisc4.11 that >> we would like to pro-actively inform users about? > > In that case shipping NEWS in libxen* would of course be fine in my > opinion even if it also includes some additional information that might > only be relevant to users of the other NEWS files. > >> I guess there is only one NEWS per source package? > > You can have `debian/<package>.NEWS` for per-binary NEWS when using > `dh_installchangelogs` or install them in some other way. But it > increases overhead and I would personally avoid having per-binary NEWS > for this reason.
Can you help me by explaining me what your current expectations regarding this issue are? You ask for not having NEWS in specific binary packages, but then subsequently explain that you'd prefer to avoid doing exactly that. Adding information to NEWS is quite an exceptional thing to happen. It's only used for cases in which the user needs to take actions or needs to be aware of a real problem that needs to be solved outside of the context of what we can do in the packaging and Debian. My opinion is that adding the extra complexity is not warranted to fix the accidental annoyance of pressing a key on the keyboard for a user who chooses to install apt-listchanges. Thanks, Hans
