Hi, I should mention that I adopted normalize-audio in 2007 and don't know much about its history (apart from what is public).
> Some debian packaged programs (e.g: ripit) optionaly use the older normalize > program. ripit does not a have a Depends/Recommends/Suggests: on normalize-audio (nor normalize). If it uses normalize(-audio), it should add the dependency and get patched to use the normalize-audio binary instead. (CC:ing ripit maintainers) > normalize-audio still understand the normalize command-line options in etch. Yes, because normalize-audio *is* normalize (the upstream name is still normalize). BTW, I think you are mistaken here: in etch, the package was already called normalize-audio, and there was no normalize package. > normalize-audio is not set as "Replace:" normalize for some reasons > (defaults..) I don't know why and I'm reluctant to add one 5 years after the name change. > It might be however useful to just notify in install time, that manually > installing an > alternative of /usr/bin/normalize to /usr/bin/normalize-audio is okay if the > user do The alternative system cannot be used, since there is no alternative setting (the monodoc package with the name conflict is not a drop-in replacement, which would be required for alternatives). Telling users to manually installing symlinks in /usr/bin is not the thing we promote (and as far as I know we do not do that for other renamed packages). I think a debconf popup on installation is too intrusive just for informing the user about the name change. The name change is documented in README.Debian. The user is free to setup symlinks in /usr/local/bin or wherever he wants. > not care about the fact that, now, compression is enabled by default (old -c > option). Which is an upstream decision completely unrelated to the name change. Joachim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
