On Mon, 28 Oct 2024 at 18:42, наб <nabijaczlew...@nabijaczleweli.xyz> wrote:
> > I've written /a/ finddup like every three months for the past few years, > and every time I'm annoyed util-linux hardlink(1) doesn't have a > "just give me the duplicate files" mode, so I just wrote it: > > https://lore.kernel.org/util-linux/5acde6a911f086ab8d2314c5b76eb76075140941.1730139540.git.nabijaczlew...@nabijaczleweli.xyz/t/#u > > hardlink(1) is a widely-used canonical implementation > with ongoing maintenance (naturally, it's in util-linux). > Hooray! > What do you consider the best way of action here? > If the patchset lands in util-linux, that renders the entire package > obsolescent. > I'd say > 1. fix the bit where finddup reads the whole file into memory > (this is in git already) > 2. don't add more binaries or whatever, > don't shim out zum like it is in git > 3. declare the package obsolescent, > > The whole thing should be explained in NEWS.Debian. > since there's a non-insignificant popcon here > 4. remove it from forky > This all sounds good to me (indeed, findstrip and findcore were quick hacks, and I'm quite happy to remove them again). This code is best left in 1996 where it came from. > > Here's a NEWS snippet: > -- >8 -- > Since trixie, the perforate package is obsolescent: > + zum-like functionality is provided by cp --sparse and --reflink > (this is the default for sparse files!) > + finddup-like functionality is provided by hardlink -lc > > Please migrate away from perforate, it will be removed from forky. > Andreas, I am of course happy to use salsa; I just hadn't worked all that out when I was last actively working on packaging. If you are happy that the package be declared obsolescent, with removal due in forky, I'm happy to do the work required to clean it up* pro tem*. I am very much in favour of removing obsolete and/or duplicate packages that are not actively maintained or obviously beloved. -- https://rrt.sc3d.org
