On Fri, 28 Dec 2001, Shachar Shemesh wrote:

> Whenever updating apackage 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.

that's easy, assuming people compile it as root, and not under their own
home directories.

> 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.

sounds easy enough.

> 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.

ough, CVS? who's managing the modules there anyway?

> 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?

since shlomi's already compiled it from source, using SRPMs would be
pointless. besides, it _seems_ to me that RPMs for openssh lag behind, and
thus it'll be better to install this one package from source, rather then
from RPMs. note that i looked at RPMs, not at SRPMs.

in any case, please don't maintain a dual system - either from tgz, or
from RPM - but not both. its enough that you coordinate this with shlomi,
and after you're done, just let the rest of us know what you did.

--
guy

"For world domination - press 1,
 or dial 0, and please hold, for the creator." -- nob o. dy


----------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED]
Archives available at http://www.mail-archive.com/[email protected]/

Reply via email to