Package submissions Was: 2004051405191026954 mnemoc msg what about the checksums?

Hi,

first read a bit from our submaster system:

On: Fri, 14 May 2004 17:18:35 +0200,
    [email protected] wrote:
> Rejected Patch: 2004051405191026954 [by tschmidt]            + tschmidt
> 
> Tobias Schmidt:
>      Added Package libgift (FastTrack /
>  Gnutella Filesharing)
>      Added Package apollon
> (KDE-UI for filesharing via libgift)
>      Added Package xrootconsole
> (watch your syslog in your root-window)
> 
> VOTECHECK: Don't know responsible user for package/tschmidt/
> xrootconsole/Makefile.patch!
> VOTECHECK: Don't know responsible user for package/tschmidt/
> apollon/apollon.desc!
> VOTECHECK: Don't know responsible user for package/tschmidt/
> libgift/libgift.desc!
> VOTECHECK: Don't know responsible user for package/tschmidt/
> xrootconsole/xrootconsole.desc!
> VOTECHECK: Don't know responsible user for package/tschmidt/
> xrootconsole/xrootconsole.conf!
> 
> (rene) +prefic=/usr ? aside this should have been prefi_x
> packages in ROCK Linux are suppost to be prefix aware, that
> means a user can just build with -prefix=/opt/s.th. and
> expect the package there; patch not in unified format; and
> the .desc files in general are a bit white-space (enter)
> filled ...
> (rene) "Too lazy too look who he is..." you should no be too
> lazy if you want to submit packages!
> (mnemoc) what about the checksums?
  Yes, those, too.

And now let's discuss how packages should be submitted (I will add
this to the handbook, soon):

1. Make sure the Author and License are 100% accurate! And when you
   verified, take a look a 2nd time. Listing the correct original
   author and license is vital for the legal state of ROCK Linux.

2. Make sure all your tags and code is correct. Build it (yes!)
   please at build it once! And when it build read your code a 2nd
   time to ensure it did not build by accident and does not contain
   typos (like prefic).

3. Implant a checksum for the downloaded files:
   ./scripts/Create-CkSumPatch pkg-name | patch -p1
   This is important to track corrupted downloads and security
   problems

4. Implant a correct copyright text:
   ./scripts/Create-CopyPatch pkg-dir | patch -p1

5. Please try to indent the .desc file in a readable format, this
   it not too many stray whitespaces / newlines and not more then
   80 chars/row and such. The common newline coverage is:

[I] 

[T] 
[T] 

[U] 

[A] 
[M] 

[F] 
[R] 

[C] 

[L] 
[S] 
[V] 
[P] 

[D] 

   or so. At least not multiple successive newlines.

(And yes, some of my gcc-3.4 patches violate at least the checksum
creation point; but while working three days on 80+ patches I hope
you can excuse this ... ;-)

Sincerely yours,
  René Rebe
    - ROCK Linux stable release maintainer

--  
René Rebe - Europe/Germany/Berlin
  [email protected] [email protected]
http://www.rocklinux.org http://www.rocklinux-consulting.de

> 
> ----------------------------------------------------------------------------
> https://www.rocklinux.net/submaster/smadm.cgi?i=2004051405191026954
> _______________________________________________
> rock-sm mailing list
> [email protected]
> http://www.rocklinux.net/mailman/listinfo/rock-sm