Dan Price wrote: > On Fri 18 Jan 2008 at 10:07AM, Chris Quenelle wrote: >> For now, I'm planning on using traditional Solaris packages, >> and uploading them with pkgsend. I'm curious what the next >> step after that is. >> >> I'm interested in a standard format for something my Makefiles >> can produce, that can later be uploaded. I'm assuming this >> would be the logical equivalent of: >> a tarball >> a manifest (for checking) >> any necessary metadata for dependencies, etc > > At some point I suggested zip or jar, with a metadata file. Since > they are univerisally producable.
That sounds like a good idea, but it's completely orthogonal to my point. My point was: 1) If you don't standardize this format, it won't be interchangeable. And 2) Having this format be interchangeable produces significant benefits for the community. > >> Can I use an installed IPS package to create a new IPS package >> on a new server? > > Not necessarily-- packages may not be fully, in the traditional sense, > installed. For example, a package might include 64 bit binaries. On > a 32-bit system, IPS could omit the 64 bit binaries due to its filtering > capabilities. Okay. If I wanted to use "pkg install" to port a package from one repository to another, I might need to add an install option that say "get all bits regardless". Is there a way to do a simple upload from an "installation" to a server that automatically includes the original metadata? I'm wodering if I can use an archive of a server directory as an internal build output. I could have my build run a local server, upload my files to it, then archive the server database. It's a stupid idea, I'd rather have a portable on-disk format. But rolling my own zip-file/metadata format is throw away work. > > -dp > _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
