Re: Orphaning php-codesniffer, then take it over by the PHP PEAR team
Thomas Goirand <email@example.com> writes:
> By the way, do other think that, even in this case, I should keep the
> as minimum as possible? Or is it ok, considering that all of our
> toolsets have
> changed since the last upload (eg: we now have pkg-php-tools and dh 8
> sequencer), that we do a bit more changes in the package than just the new
> upstream release?
Since the package has been unmaintained for years, and from what I've
read so far, it does seem that it will end up under a team's umbrella
anyway in a month's time, I wouldn't care about any possibly hurt
feelings, and update the packaging to current practice.
Quality and maintainability should come before the letter of any NMU
recommendations and best practices.