Brian Smith wrote:
[email protected] wrote:
Brian,
The pkg(5) software already runs on Solaris 10 (actually Solaris 9 too).
The unit test cases all pass. So there shouldn't be any reorganization
required as mentioned in point 5. We have a self-contained set of IPS
packages for Solaris 10 (see ipshowto.org) that includes a minimized
python and the components needed by pkg(5) (pyOpenSSL, cherrypy, etc.)
Thanks for the reply, Tom. I am aware of the ipshowto.org site and the work
to make pkg(5) portable. That definitely makes the job a lot easier.
However, the ipshowto.org site doesn't provide a simple way to install
pkg(5)--or, at least, the way it provides is not as simple as it could be.
1. Download the zip file:
http://download.java.net/updatecenter2/promoted/B18/pkg-toolkit-2.1-b18-sunos-i386.zip
2. Unzip it wherever you want, e.g., /opt.
3. Run the tools: e.g., /opt/pkg-toolkit-sunos-i386/bin/pkg
Granted, this isn't an SVR4 package, and it doesn't put the binaries
into /usr/bin, /usr/lib, etc. It seems that what you want is:
1. Download the SVR4 package file: ...
2. pkgadd -d downloaded-file.pkg (this installs SUNWipkg, etc.)
3. Run the tools: e.g., /usr/bin/pkg
Also, from reading the website I got the impression that the distribution of
pkg(5) on ipshowto.org cannot automatically upgrade itself.
On the contrary, it certainly can upgrade itself. From the above, one
would do:
cd /opt/pkg-toolkit-sunos-i386
bin/pkg image-update
I want to
package it as a SRV4 package that can be installed (and uninstalled) with a
one-liner on the command line, and that can be upgraded using pkg
image-update.
I think the vast majority of the work will go into building the
bootstrapping installer and the integration with the OpenSolaris website.
Agreed. Plus creating packages that have the file layout that you want,
assuming you want the same file layout that OpenSolaris uses.
I
can build the installer myself. But, will I be able to host it on the
OpenSolaris website? Will I be able to update the documentation for people
building IPS packages to explain how to build IPS packages that work on
Solaris 10, or that explicitly indicate that they *won't* work on Solaris
10?
However, you would probably want something that is more integrated with
the operating system.
Besides the easy installation, I think less OS integration is better than
more OS integration, because Solaris 10 support contracts will not cover
packages installed by pkg(5).
By "more integrated", I was talking about having the binaries in
/usr/bin rather than something like /opt/pkg/bin.
If you could live with /opt/pkg/bin, it would be pretty easy to create
an SVR4 package that would include a pre-installed IPS image (fully
updatable) that lives at /opt using the UC2 packages that already exist.
The "pkg-toolkit-sunos-i386" pathname above is just what we have in our
ZIP file; that isn't part of the package.
Tom
I want to ensure that IPS doesn't reduce the
supportability of the system when running on Solaris 10. In particular, no
use of IPS should result in problems with applying official SunSolve
patches. That is why I want SUNWipkg on Solaris to refuse to install or
update any of the packages that covered by the Solaris 10 support contract.
I want to review the code to make sure that when it runs on Nevada, it
doesn't do anything that technically works but would go against the
supportability guidelines. This will help make Solaris 10 users confident
about installing IPS on their systems. This is what I meant about
compartmentalizing Indiana-specific behavior.
Thanks,
Brian
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
