On Fri, 28 Dec 2001, Shachar Shemesh wrote: > Hi all, > > In order to make maintanace of the system easier (being as it is that > there are multiple administrators here), and to avoid cases such as the > mirror wiping incident from recurring, I suggest the following procedures. > > Whenever updating paackage from sources, leave both the downloaded > source file, and the opened directory in which you compiled it under > /usr/src or /usr/local/src (I noticed they are different filesystems), > depending on whether you eventually intend to install it into /usr/ or > /usr/local.
/usr/local . Leave /usr to RPMs. That way there will be no clashes between what is managed by rpm and independent packages (except on /etc) > > Create a small one line file called "compile.sh". I use the "sh" > extension, even though I don't make it a script file proper, so that it > will stick out when doing "ls". doing "source compile.sh" should ready > the source tree for installation. I.e. - the way to repeat your exact > install, including excat install parameters, will be to do "source > compile.sh ; make ; make install". This way, you leave an audit trail of > your actions. > > Assuming that we adopt mulix's CVS idea, the compile.sh file should be > checked into the CVS (but not the rest of the source tree), as it shoudl > contain all the information necessary to rebuild a package. > > On a different note: > For the SSH cleanup I promised (my two days of sitting onmy hands are > up ;), I am going to overwrite the RPMs for openssh. I was considering > getting the SRPMs from the openssh site, but I am not sure this is a > good idea. Feedback, anyone? Try rebuilding redhat's SRPMs from 7.2's updates directory. Still inpect it before you try to install it (rpm -qpl package.rpm , rpm -qp --scripts package.rpm) . It is recommended not to build RPMs as root: the process of creating an RPM package involves installing the package under ome temporary directory before packaging it. If, due to some screw-up in the generated script, it tries to install the files on the real system and you build it as a user, you get an "access denied" message, and that's it. If you are root: access is never denied... Also: it is enough to leave the source RPMs (if you had to modify them) as they generally allow to fully reconstruct the build process (unlike debs, where the building process allows you to "cheat" and modify the tree between different phases). The equivalent of compile.sh here is the rpm spec file. -- Tzafrir Cohen mailto:[EMAIL PROTECTED] http://www.technion.ac.il/~tzafrir ---------------------------------------------------------------------------- To unsubscribe, send a message to [EMAIL PROTECTED] Archives available at http://www.mail-archive.com/[email protected]/
