Then there's the overly-complicated mechanism, solaris.py, which we've been
using to suck in the WOS, do a bunch of magic on it, and spit out the
redistributable bits that you see on pkg.opensolaris.org. As Bart and
David would likely be the first to tell you, it's a royal pain in the butt,
and at thois point requires that you do a full WOS import along with
whatever else you're trying to do.
I was actually able to create a simple 30-line wrapper for solaris.py
that does not require a full WOS import. For each package in a
directory, just create files for each package with the following entries:
package SUNWxyz > SUNWxyz
import SUNWxyz >> SUNWxyz
end SUNWxyz >> SUNWxyz
Then create a product list with entries for each file created above:
include SUNWxyz >> product.list
You can then run solaris.py with all these options:
solaris.py -s <repo> -w <SVR4 pkg location> -v <OS> -b <VERSION>
product.list
If we get the wiki going, I can post the script.
-- Alan
Danek Duvall wrote:
On Mon, Nov 26, 2007 at 06:34:14PM -0800, Chris Quenelle wrote:
I'm looking into what it would take to release Sun Studio compilers and
tools using IPS. I was wondering if there was any SYSV package converter
scripts (even partially working ones) that I could play with.
There are two ways to convert svr4 packages, other than by hand. The
extremely simple thing we got going first was "pkgsend send" (yeah, dumb
name -- blame me), which takesa a svr4 package in whatever format, and
dumps the contents into IPS. It's not terribly bright, though, and doesn't
give you a chance to diddle with the package at all (change the name, add
or remove actions, etc)., and may even get things like BASEDIR horribly
wrong. We haven't used it in months, and it probably should be torched at
this point.
Then there's the overly-complicated mechanism, solaris.py, which we've been
using to suck in the WOS, do a bunch of magic on it, and spit out the
redistributable bits that you see on pkg.opensolaris.org. As Bart and
David would likely be the first to tell you, it's a royal pain in the butt,
and at thois point requires that you do a full WOS import along with
whatever else you're trying to do.
I'm in the process of trying to get something sane out of this mess, but
it's going to take a little time. You're welcome to play with what's
there, but it's decidedly not ready for prime-time yet. It may still be
enough to get you some useful information, though.
If there's a Sun internal alias I should be on please let me know.
It's been defunct since this list started. If you have confidential things
you need to discuss, feel free to send it to us individually.
Do people expect a SYSV->IPS package converter will be good enough to
actually base a release on it while we get our packaging infrastructure
converted over to create native IPS packages?
I think that's a reasonable goal, and probably necessary as well.
Or should I jump straight to integrating IPS "the right way" in our build
system (takes longer)?
It's probably worth waiting for the pkgsend rewrite, but even though that's
my top priority right now, I still wouldn't hold my breath. And a hunger
strike ain't gonna get it done faster, neither. ;-)
P.S. I was playing with IPS and wanted to test out the indiana depot,
and I couldn't find the URL of the depot anywhere on the web pages
on osol.org.
Hunh. We should obviously add that somewhere. I guess we just figured
that most people would be starting from an indiana base and wouldn't need
it. Until that's fixed, it's pkg.opensolaris.org (and we have an internal
mirror, ipkg.sfbay, aka pkg5.sfbay).
The IPS hg repo also wasn't very well published.
Did you find our project page easily enough?
You might want to consider starting up a wiki on wikis.sun.com.
That would make it much easier to keep the web pages up to date.
Any Sun employee can go create their own wiki area.
I'm not sure I see why splitting our documentation up into multiple places
would make it any easier to find. I'd never think to look at wikis.sun.com
for details on an opensolaris project. And then it's limited to Sun
employees, which is unfriendly in a different way.
Danek
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
