openssh unix dev - Mar 2001 - suggestion: saving old binaries during installation

Just as a suggestion, I liked the way the ssh.com's ssh would move the
old binaries to filename.old then install the new ones....so that way
you have an old copy to revert back to if needed (without copying them
all by hand).

And that's exactly what a make install (IN THE SOURCE CODE DIR) will do. 

Donald.Smith at qwest.com IP Engineering Security
303-226-9939/0688 Office/Fax
720-320-1537 cell
> -----Original Message-----
> From: Kevin Taylor [mailto:ktaylor at eosdata.gsfc.nasa.gov]
> Sent: Tuesday, March 06, 2001 12:37 PM
> To: openssh-unix-dev at mindrot.org
> Subject: suggestion: saving old binaries during installation
> 
> 
> 
> Just as a suggestion, I liked the way the ssh.com's ssh would move the
> old binaries to filename.old then install the new ones....so that way
> you have an old copy to revert back to if needed (without copying them
> all by hand).
>

Circa 2001-Mar-06 14:36:50 -0500 dixit Kevin Taylor:

: Just as a suggestion, I liked the way the ssh.com's ssh would move
: the old binaries to filename.old then install the new ones....so
: that way you have an old copy to revert back to if needed (without
: copying them all by hand).

I would recommend instead installing the "new" binaries to a different
spot and using something like epkg <http://www.encap.org/epkg/> to
symlink the binaries into the usual spot:

  ./configure --prefix=/usr/local/encap/openssh-2.5.1p2 [...]

See the epkg website for further info.
  
-- 
jim knoble | jmknoble at jmknoble.cx | http://www.jmknoble.cx/

kevin your right. The Makefile for ssh-1.2.31 does copy current FILENAME to
FILENAME.old then cp binaries around but the
Openssh Makefile doesn't.
The make install part of the Openssh's Makefile just calls install-sh it
would be fairly trivial to fix the install-sh to make backup copies of the
binaries. I have been spending too much time between the Openssh code and
ssh.com's code. 
Sorry for the confusion.

Donald.Smith at qwest.com IP Engineering Security
303-226-9939/0688 Office/Fax
720-320-1537 cell
> -----Original Message-----
> From: Kevin Taylor [mailto:ktaylor at eosdata.gsfc.nasa.gov]
> Sent: Wednesday, March 07, 2001 6:41 AM
> To: Smith, Donald
> Cc: 'Kevin Taylor'; openssh-unix-dev at mindrot.org
> Subject: Re: suggestion: saving old binaries during installation
> 
> 
> "Smith, Donald" wrote:
> > 
> > And that's exactly what a make install (IN THE SOURCE CODE 
> DIR) will do.
> > 
> > Donald.Smith at qwest.com IP Engineering Security
> > 303-226-9939/0688 Office/Fax
> > 720-320-1537 cell
> > 
> > > -----Original Message-----
> > > From: Kevin Taylor [mailto:ktaylor at eosdata.gsfc.nasa.gov]
> > > Sent: Tuesday, March 06, 2001 12:37 PM
> > > To: openssh-unix-dev at mindrot.org
> > > Subject: suggestion: saving old binaries during installation
> > >
> > >
> > >
> > > Just as a suggestion, I liked the way the ssh.com's ssh 
> would move the
> > > old binaries to filename.old then install the new 
> ones....so that way
> > > you have an old copy to revert back to if needed (without 
> copying them
> > > all by hand).
> > >
> 
> 
> but it doesn't.
> 
> 
> -- 
> ---------------------------------------------------------.
> Kevin Taylor                                              \
> Systems Administrator - DAAC, Code 902, Bldg 32, Rm N126A /
> Science Systems and Applications, Inc.                    \
> Goddard Space Flight Center                               /
> Greenbelt, MD 20771                                       \
>                                                           /
> Phone:  (301) 614-5505                                    \
> e-mail: ktaylor at daac.gsfc.nasa.gov                        /
> ----------------------------------------------------------'
>