An introduction of the new cheerleader...

[Alan Cox]

On Mon, Jan 26, 2004 at 09:40:48PM +0100, Michael Schwendt wrote:
> I'm also a fan of automization, but (1) you cannot automate everything,
> and (2) automization which saves one party time, should not increase the
> work-load for another party. So, afterall you must have precize ideas on
> how you would like to contribute packages. If, for instance, submitting
> automated package request tickets result in overloading the queue for
> reviewers or poor communication between packager and QA, that would be a
> bad thing. Automization seems suitable for people with commit-access to a
> build-system.

Remember that every perl package you generate means a package you have
to handle bugs for and a package that may need a security audit and so on.

I agree CPAN in RPM has enormous value - providing people treat it like
CPAN - ie with a lot of suspicion unles the module author is well known 8)