On Tue, Jan 07, 2003 at 11:55:12AM +0100, Rafael Garcia-Suarez wrote: > Nicholas Clark <nick@ccl4.org> wrote: > > > I wonder whether the perl team (us actually) could take on the > > > responsibility of packaging perl for RH so we don't have to dance around > > > RH decisions...? > > We already do. It's called ./Configure && make && su root -c 'make > > install' Nothing wrong with your own perl in /usr/local if you don't like > > RedHat's. > I've always done this on all machines I had root access to ;-) The reason for packaging is to give "end consumers" an easy way to install it. > However I imagine we could ship a _simple_ _sample_ spec file (as other > popular source packages do.) Nothing complicated (no splitting in multiple > .rpms, etc.) This does sound like a good idea, but it hides some nasty pitfalls. Perl has become a too important part of every system today, which means that we shouldn't allow people to disable all their perl scripts by accident (i.e. providing a perl.spec means testing it on the most popular rpm distributions). Furthermore every vendor has already packaged perl, and will stick to his schema due to portability concerns. Maybe one should look at the current perl.spec as provided by some vendors and compare them. But I think that you cannot avoid becoming vendor dependend in the spec file. It might be interesting to try an lsb packaged perl (http://www.linuxbase.org/appbat/index.html). > Something that could be used simply as : > $ tar zxf perl-5.9.0.tar.gz > $ cp perl-5.9.0/contrib/perl.spec /usr/src/redhat/SPECS > $ mv perl-5.9.0.tar.gz /usr/src/redhat/SOURCES > $ rm -rf perl-5.9.0 > $ cd /usr/src/redhat/SPECS > $ rpm -bb --clean perl.spec > $ cd ../RPMS/i386 # or whatever > # rpm --force --nodeps -Uvh perl-5.9.0.rpm # potentially dangerous If perl will come with its own (single) spec file, then you can even simplify this to rpmbuild -tb perl-5.9.0.tar.gz rpm -Uvh /usr/src/redhat/RPMS/i386/perl-5.9.0.i386.rpm -tb looks for a specfile in the tar.gz (actually just something ending in .spec), extracts it and does the steps you wrote above. -- Axel.Thimm@physik.fu-berlin.de