openssh unix dev - Oct 2003 - OpenSSH package

A non-text attachment was scrubbed...
Name: not available
Type: text
Size: 7366 bytes
Desc: not available
Url :
http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20031015/02b75f40/attachment.ksh

Henry Grebler wrote:
> I saw that you have a variable TEST_DIR and a way of building a
> package using that, but I had hoped to test the package and then
> install it, not test one package and install another. I don't think it
> would have got around the chroot problems.
Apparently SCO Unixes have pkgadd which doesn't support -R, which is why
TEST_DIR is there.
> Anyway, I was able to achieve all my goals, and your package made it a
> lot easier than doing it manually. So, thanks again.
I wrote a wrapper for testing such configurations, see:

http://marc.theaimsgroup.com/?l=openssh-unix-dev&m=102698517600349

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

On Wed, 15 Oct 2003, Henry Grebler wrote:
> I saw that you have a variable TEST_DIR and a way of building a
> package using that, but I had hoped to test the package and then
> install it, not test one package and install another. I don't think it
> would have got around the chroot problems.
I put TEST_DIR in to address the very problems you report.

As Darren said, the -R option to pkgadd is not available on all
the platforms the buildpkg.sh script supports.

-- 
Tim Rice				Multitalents	(707) 887-1469
tim at multitalents.net

> First of all, thank you for your contribution of the OpenSSH package
> for Solaris. It is very useful.
>
Darren and Tim added most of the nicer features after I gutted the
existing build script to make it FAKE ROOT based.

[..]
> I am building a Solaris 9 server. Solaris 9 comes with ssh, so I want
> to test my recent build of OpenSSH before replacing Sun's native ssh.
> I tried to install into /tmp/hmg.
>
> It seems that the package makes some assumptions: that root_path will
> be used as a chroot newroot; that certain directories in
> $root_path/etc already exist.
>
Looking below I question the use of -R.  -R is really designed for
jumpstart and other installs where the -R points to a complete OS
install.

"All files, including package system information files, are relocated to
a directory tree starting  in  the specified root_path."

[..]
> I saw that you have a variable TEST_DIR and a way of building a
> package using that, but I had hoped to test the package and then
> install it, not test one package and install another. I don't think it
> would have got around the chroot problems.
>
Actaully it would.  TEST_DIR disables the "chroot" enabled by -R.

As for your original idea.  It's too bad pkgadd does not support the -n
version from pkg_add in *BSD.

     -n      Don't actually install a package, just report the steps that
             would be taken if it was.


Or the idea like -vVAR=VALUE ala awk.

However, I guess I do business different then you do.  I then to give a
box over to testing that is non-critical.  So I can test the package in
multiple different mode.  So I can't really give you much advice.

- Ben