Hi Reuben, thank you for your very helpful hint!
Am Sat, Oct 26, 2024 at 03:44:11PM +0100 schrieb Reuben Thomas: > On Thu, 24 Oct 2024 at 18:03, Andreas Tille <[email protected]> wrote: > > > I'm interested in salvaging your package perforate, in accordance with > > the Package Salvaging procedure outlined in the Developers Reference[1]. > > That would be great! :-) > I have done quite a bit of work on this package that has not been released > in Debian, largely, I suspect, because it involves a name change. > > See https://github.com/rrthomas/finddup I guess you know perfectly why we (currently - I try to work on this) are keen on avoiding name changes. > The main points are that a) there was never a program called 'perforate', > b) the program 'zum' that did the "perforating" is now otiose, as file > systems and cp between them take care of this functionality, and so c) the > useful functionality left in the package was mainly the 'finddup' program, > which I have updated, along with the minor utility 'findstrip', and the > 'findcore' script which I've added to my version of the package. What do you consider the best way of action here? For the moment I wonder whether we keep the source+binary package name perforate (even if I confirm this name does not make much sense), point the watch file to your fork, and deliver finddup, findstrip and findcore inside the binary package perforate. The whole thing should be explained in NEWS.Debian. For sure we could also create a new package finddup and make it Conflicts/Provides: perforate. I would sponsor such a package to new. But please lets maintain the Debian packaging on Salsa (and the upstream code whereever it belongs). Kind regards and thanks again Andreas. -- https://fam-tille.de
