cvs commit: ports/security/ssh2 Makefile pkg-message pkg-plist ports/security/ssh2/files patch-apps::ssh::sshd2_config patch-apps::ssh::sshfilecopy.c patch-startup::solaris::sshd2

Marius Strobl marius at
Mon Feb 20 02:38:24 PST 2006

On Mon, Feb 20, 2006 at 05:00:16AM -0500, Kris Kennaway wrote:
> On Mon, Feb 20, 2006 at 10:38:42AM +0100, Marius Strobl wrote:
> > > > Yes, the package builders should no longer report left over files
> > > > as a side-effect. But is a port really required to clean up such
> > > > files, i.e. files like modified config files, certificates, etc
> > > > that in a real installation aren't removed on deinstall but the
> > > > user is informed to remove manually, in the package building
> > > > environment?
> > > 
> > > Yes :) The less manual work for the user the better, so when the files
> > > are unchanged from the "default" versions they should be removed
> > > automatically.
> > > 
> > 
> > Well, that's what the ssh2 port did and does as far as possible,
> > i.e. for the config files. But generally if there's any host
> > specific file which is automatically created during install of
> > the port (host key, certificate, config file with ip address, ...),
> > i.e. files were there's nothing like a "default" version and
> > which you also don't want to re-generate with every update of
> > an already installed port, do these really need to be wrapped
> > in #ifndef PACKAGE_BUILDING, moved to the startup script, etc or
> > can the warnings from the package builders just be ignored?
> Just as with your fix here, host-specific stuff needs to be done at
> package install time on the host; otherwise, it will either be omitted

Well, this neither was broken with what the ssh2 port previously did
as the package still created the host key on install if not already
existent on the host via an @exec in the pkg-plist.

> altogether from the package and the users left scratching their head
> wondering how to recreate it by hand after package install, or the
> version from the machine that built the package will be packaged and
> incorrectly used on the user's machine.

Ok, I give up. I just accept that there should be no warnings from the
package builders :)


This mail was scanned by AntiVir Milter.
This product is licensed for non-commercial use.
See for details.

More information about the cvs-all mailing list