some time ago I build RPM packages for 0.9.1. I stop it because the packages are not usable. The result were big changes for 0.9.2 to allow maintainers to build usable packages. I never tried to build RPM packages for 0.9.2.
During the time there was a more strategic change. If it is possible then we want to seperate the package stuff from the core sourcecode. Today the specs are into the source code of OpenCA :(
I would like to create seperate CVS trees for every distribution. This is more easier to handle and an RPM fix cannot crash Debian builds if it is only a RedHat specific problem. My idea is to move the complete RedHat and suse stuff to seperate directories. Example
CVS Root
========
openca-0.9
debian
Debian stuff
redhat
/modules
*.spec
/interface
*.spec
Makefile
suse
/modules
/interfaces
MakefileThis architecture would allow independent tagging for OpenCA and different RedHat, Debian etc. releases. We have also the advantage that packagemaintainers can work with a centralized CVS system. Of course we would have to do some work to extract the package code from OpenCA but it is an investment for the future and reduce the sources of errors in our make system.
Rob Thorne wrote:
* Some of the .spec files are writing files to system directories on
the build systems, which can't be right. For example, some of the
perl module RPM specs are writing to perl system directories
during rpmbuild -ba.
* Many of the spec files don't use the BuildRoot directive or the
RPM_BUILD_ROOT variable, causing the %install directives to do
funny things like write to system directories during package builds.
* Many of the "install" targets want to set group and owner even
when called for package builds. This isn't that bad, although it
does require the package builds to run as "root". Since the
scripts are otherwise also misbehaving, though, this makes running
the scripts as root a little risky :-(
It was the first time I ever build RPM packages. Install targets must include user and group permissions to establish a minimum security. How do you want to create the default permissions in the packages without the install options?
General info: I'm building on RedHat 9 using
make -f Makefile.devel rpms
This is what I want to move to redhat/. Would it be a good idea to put the stuff directly into our CVS?
Michael -- ------------------------------------------------------------------- Michael Bell Email: [EMAIL PROTECTED] ZE Computer- und Medienservice Tel.: +49 (0)30-2093 2482 (Computing Centre) Fax: +49 (0)30-2093 2704 Humboldt-University of Berlin Unter den Linden 6 10099 Berlin Email (private): [EMAIL PROTECTED] Germany http://www.openca.org
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ OpenCA-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openca-devel
