* Alan Steinberg <[EMAIL PROTECTED]> [2008-01-07 21:23]: > I can see how a basic SVR4 package can be pushed into a repository with > "pkgsend send MYsvr4pkg" . This uses the sysvpkg.py script to convert > the SVR4 package into an IPS pkg without the need for an intermediate > step. But it's actually converting the format of the package, so that a > subsequent "pkg install" treats it like an IPS pkg. > > But what if one wished to make available an existing SVR4 package > through an IPS repository, preserving the full package attributes? I > would think this can be done best by creating an IPS pkg that contains > the native package file structure. For example, an IPS package called > "MYsvr4pkg_svr4" could be created to contain the contents of > var/spool/pkg/MYsvr4pkg. The installation would then be in two steps: > > 1) pkg install MYsvr4pkg_svr4 > This would "install" the SVR4 package under var/spool/pkg/MYsvr4pkg > inside the image root > 2) pkgadd -d <image root>/MYsvr4pkg > > Am I way off here, or is that the solution that would be used? And > couldn't this solution also work for Linux RPMs and Windows MSI files?
You can embed pretty much any kind of static directory and file hierarchy into a package, so you could do what you're outlining. (I've wondered about delivering ISOs inside packages, once we have support for alternative transports.) But I'm not sure why you would embed a package in a package--that is, I'm not sure what you're attempting to enable. - Stephen -- [EMAIL PROTECTED] http://blogs.sun.com/sch/ _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
