On Saturday, July 27, 2024 11:48:29 PM MST Yavor Doganov wrote:
> Soren Stoutner wrote:
> > On Saturday, July 27, 2024 5:02:13 PM MST gregor herrmann wrote:
> > > On Sat, 27 Jul 2024 12:09:08 -0700, Soren Stoutner wrote:
> > > > 2. You have debian/baby.install, which works fine. If you have
> > > > multiple binaries you use binary-name.install for each install
> > > > file. But as you have only one binary, you can just use
> > > > debian/install if you like.
> > >
> > > Unless I'm mistaken, this will stop to work in a future debhelper
> > > compat level, so I suggest to stick to
> > > debian/<binarypackage>.install.
> >
> > That’s interesting. That is the first time I have heard that. Do
> > you have a link to any documentation?
>
> I think it's documented in debhelper-compat-upgrade-checklist(7).
> It will trigger a warning with compat level 14 and error with 15.
Thanks for the documentation.
"It now triggers a warning to use package-less versions of debhelper configuration files when there are 2 or more binary packages listed in debian/control in most cases."
Am I reading this correctly that it will still not produce a warning for packages like baby that only have 1 binary package?
--
Soren Stoutner
soren@debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part.