Hi Andreas
I admit I share the old fashioned view and we asket Jelmer to not
run Janitor on Debian Med and R-pkg-team. The rationale is that
we are running
routine-update
on all our packages. Routine-update is running all scripts that are
called by Janitor and thus you have the same effect.
It's not quite the same effect.
While there is a substantial overlap in the feature sets, one is not a
subset of the other.
- routine-update does some great things like normalising packaging.
That's something Janitor can't do because people would scream about an
automated tool touching their precious whitespace.
- Janitor applies multi-arch hints, and looks at obsolete versioned
dependencies — these are things that routine-update can't do because it
doesn't have a holistic view of the archive. Janitor is also run
automatically rather than only when the maintainer is seeking to update
the package, meaning that improvements can accrue over time. Janitor
updates also cause CI to be run, meaning that regressions such as a
FTBFS caused by other packages changing get spotted earlier.
I don't see any reason to say that tools are mutually exclusive — let's
let Janitor make improvements and when packages need updating, we can
have routine-update make some more?
regards
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ [email protected]
Debian Developer http://www.debian.org/ [email protected]
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
