[IPCop-cvs] ipcop/doc How-to-make-update,1.2,1.3

[Franck B. <fra...@us...>]

Update of /cvsroot/ipcop/ipcop/doc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv28369/doc

Modified Files:
	How-to-make-update 
Log Message:
Forward changes from 1.4. Ok there is no patch, no list of updated files (ROOTFILES).
The loop checks existence of 'setup-X' and computes the corresponding patch. No 'setup-X',
no patche, no message !  (X is 0..9)


Index: How-to-make-update
===================================================================
RCS file: /cvsroot/ipcop/ipcop/doc/How-to-make-update,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** How-to-make-update	29 Mar 2005 18:44:44 -0000	1.2
--- How-to-make-update	31 Jul 2005 12:47:21 -0000	1.3
***************
*** 1,5 ****
  Prerequisites
  - have release right on sourceforge to be able to affect uploaded files to a release
! - have private gpg key (and password) to sign the patch, import the key with gpg --import (private key file name)
  
  Build
--- 1,7 ----
  Prerequisites
  - have release right on sourceforge to be able to affect uploaded files to a release
! - have 'IPCop development Group' private gpg key (and password) to sign the patch, import the key with gpg --import (private key file name)
! - you can create your own key (named 'IPCop development Group') and replace (temporarily!) the pub key in 
!   your box (/root/.gnupg/*) for testing your patch
  
  Build
***************
*** 12,15 ****
--- 14,18 ----
  - manually check all necessary files are include in updates/1.4.x/ROOTFILES.*.1.4.x comparing with /doc/updated-sources.txt
  - sign the patch with gpg --local-user "IPCop Development Group" --sign update-1.4.x.tgz
+   or simply typing ./sign    (make.sh produces 'sign' batch file for convinience)
  
  Sourceforge