On Tue, Aug 20, 2024 at 12:26:39 +0100, Jonathan Dowland wrote: > On Sun Aug 18, 2024 at 5:32 PM BST, Greg Wooledge wrote: > > On Sun, Aug 18, 2024 at 17:08:00 +0100, Jonathan Dowland wrote: > > > I've long felt that they were overcomplicated in themselves: the > > > ideal UX should be not much more than "equivs package-name" => > > > ./package-name.deb generated, IMHO. I once had ambitions to add > > > that UX (either as a patch to equivs, or as a separate equivs-ng) > > > but I never got around to it. > > > > That may be acceptable for packages that don't have any Depends: or > > Provides: lines or what-have-you. > > I would want this for packages which had depends/provides as well: my > expectation would be that the generated dummy package would also have > those depends/provides. It must not have been clear from my brief > illustration, but my envisaged "equivs" tool would look up the package > name from dpkg metadata.
This is getting weirder. You're saying that you use equivs to create packages that have the SAME NAMES as Debian packages??
