Author: pawelz Date: Tue Feb 23 10:28:26 2010 GMT Module: PLD-doc Tag: HEAD ---- Log message: - s/SOURCES/packages/
---- Files affected: PLD-doc: devel-hints-en.txt (1.39 -> 1.40) , devel-hints-pl.txt (1.59 -> 1.60) ---- Diffs: ================================================================ Index: PLD-doc/devel-hints-en.txt diff -u PLD-doc/devel-hints-en.txt:1.39 PLD-doc/devel-hints-en.txt:1.40 --- PLD-doc/devel-hints-en.txt:1.39 Mon Feb 8 11:43:20 2010 +++ PLD-doc/devel-hints-en.txt Tue Feb 23 11:28:21 2010 @@ -94,7 +94,7 @@ Package groups: -A package must have a defined Group field according to SOURCES/rpm.groups +A package must have a defined Group field according to packages/rpm.groups We don't include "BuildRequires: kernel-headers" in packages cointaining user-space applications. Such dependency can only be included in packages @@ -646,7 +646,7 @@ Apache version independant packages NB: there's webapps framework now (template-webapp.spec) -http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/webapps.README +http://cvs.pld-linux.org/cgi-bin/cvsweb/packages/webapps/webapps.README You should use this when making apache packages. and this apache section needs updating. @@ -680,7 +680,7 @@ */ -Naming files in SOURCES. +Naming files other than .spec A few unjustified conventions: - NAME-foo.patch - patches @@ -693,10 +693,6 @@ group like, php-pear-%{_pearname}, perl-%{pnam}, python-%{_name}. Having patches sources prefixed with package name also avoids file collisions between different packages. - -One of the reasons is because it's convinient to vi ../SOURCES/NAME-<TAB> to -get list of patches and vi ../SOURCES/NAME.<TAB> to get your shell expand -config files. Please try to follow this, as then if there's planned massive changes to all crontab, initscript or sysconfig files, then the files are easily located from ================================================================ Index: PLD-doc/devel-hints-pl.txt diff -u PLD-doc/devel-hints-pl.txt:1.59 PLD-doc/devel-hints-pl.txt:1.60 --- PLD-doc/devel-hints-pl.txt:1.59 Wed Feb 10 21:24:35 2010 +++ PLD-doc/devel-hints-pl.txt Tue Feb 23 11:28:21 2010 @@ -92,7 +92,7 @@ Grupy pakiet�w: -Pakiet musi posiada� zdefiniowane pole Group: zgodnie z SOURCES/rpm.groups +Pakiet musi posiada� zdefiniowane pole Group: zgodnie z packages/rpm.groups Nie umieszczamy "BuildRequires: kernel-headers" w pakietach z samymi @@ -624,7 +624,7 @@ Pakiety niezale�ne od wersji Apache NB: there's webapps framework now (template-webapp.spec) -http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/webapps.README +http://cvs.pld-linux.org/cgi-bin/cvsweb/packages/webapps/webapps.README You should use this when making apache packages. and this apache section needs updating. @@ -691,7 +691,7 @@ template-apache-package.spec). -Nazewnictwo plik�w w SOURCES +Nazewnictwo plik�w innych ni� .spec Kilka bezpodstawnych konwencji: - NAZWA-foo.patch - �atki @@ -704,10 +704,6 @@ pakietu jest poprzedzona prefiksem grupy (np. php-pear-%{_pearname}, perl-%{pnam}, python-%{_name}). Poprzedzanie nazwy �r�de� i �at nazw� pakietu pozwala unikn�� kolizji pomi�dzy r��nymi pakietami. - -Wygodnym jest u�ycie vi ../SOURCES/NAZWA-<TAB> dla uzyskania listy �at -oraz vi ../SOURCES/NAZWA.<TAB> aby pow�oka rozwin��a list� plik�w -konfiguracyjnych. Zaleca si� stosowanie tej konwencji. Gdyby okaza�a si� konieczna masowa zmiana plik�w crontab, skrypt�w inicjalizacyjnych czy te� sysconfig, ================================================================ ---- CVS-web: http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/PLD-doc/devel-hints-en.txt?r1=1.39&r2=1.40&f=u http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/PLD-doc/devel-hints-pl.txt?r1=1.59&r2=1.60&f=u
_______________________________________________ pld-cvs-commit mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit
