Hello,
I filed bug 9777 but then thought perhaps this would be better
suited to a discussion here:
Talking to many customers, I've found that tarballs reign for many shops
who are cross platform. Talking with Bart certainly he suggest but why
would anyone want to use something other than IPS. To ease the transition
pain for folks used to un-taring a tarball during an install (with
arbitrary scripting), would an easier interface to turn a tarball into a
package be a sane offering? This is something the install team gets
questioned about often with the removal of post-install scripts.
I envision a pkgsend option to publish a package whereby either a tarball
is given (with absolute paths assumed) or a root for the tarball is given;
then all the files are rolled up into a package. I'm not sure whether
dependency checks would be necessary or not. (I suspect doing a solaris.py
dependency check run would be good.) My only thought is perhaps this
should be an interactive tool so that a user can mark volatile files
during package creation (i.e. generates a manifest for the user).
I'm curious to hear feedback on these ideas and generate a good clear path
to present for users who've wedded themselves to tarballs but could use a
way to IPS.
Thank you,
Clay
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
