[repo-coord] Packaging Process - PLEASE READ

[Bent Terp]

On Fri, 2004-05-21 at 04:47, Rudolf Kastl wrote: 
> 1. we need to specify checks for the source code. Means checking if the
> source is alright or no in terms of malicously changed.

GPG sigs? MD5 checks? What else should I consider?

> 2. before you even touch the source check if its already packaged.

Bien sûr, life is short.

> 1. perl and sed should be avoided

Disagree. Again, life is short and a perl one-liner is much more
resilient than a patch - e.g. " find . -name \*.h | xargs -i{} perl -pi
-e 's[/usr/local][/usr]' {} " is more likely to survive a
version-update. 

> 2. buildmacros should all be defined on top of the spec.

I'll sort of buy that, assuming you mean "at the top of the spec".

> there can be exclusions when its not possible to
> act otherwise in a special case. 

How kind of you ;-) I use /etc/macros on the buildboxes to keep track of
which distro's installed - DAR and MACH are too difficult for me.

> 3. other major distros should be checked

There's a lot of treasure to be found in suse contribs and mandrake
cooker. But their weird macros give me loads of grey hair.

> 1. building should always happen in a non root environment

This sentence uses the word "should" with the same strength as in an
RFC: "should" = "absolutely always must". Which is why I haven't rebuild
OpenPBS from the oscar.sf.net distribution, yet.

> 3. it has to be verified that the rpm installs clean and runs fine
> before its released.

And perl module authors should ensure that their modules test out okay
before dumping them in CPAN! 

>  That includes basic functionality checking.

I try, and often fail ;-)


-- 
/Benty