Bart Smaalders wrote:
We have had this conversation before....
Philip Brown wrote:
There are some things that are purely one-shot operations unique to a
particular piece of software.
But the person packaging the software is often incapable of correctly
writing this one-shot operation in any context, perhaps except that
of live multi-user level installation
And that is Just Fine, because wrapping them in an appropriate actuator,
means that they will run "normally", when the system is up and live.
We're _not_ supporting, allowing, permitting or condoning arbitrary
install time scripting in packages.
you cant DISallow it. the mechanism is there already, inherent in the
design. As Nicole(?) acknowleged a while back, it is possible to write an
actuator wrapper to encapsulate pretty much all postinstall scripts.
I believe she offered to write a standard actuator wrapper for it, and you
said no dont write it.
But someone eventually will.
So.. you dont have a choice of "disallowing" it. your only long term choices
are, to either
- write it up front, and thus have some level of influence to encourage
people, "here it is, but you'll be better off using the following
mechanisms, in these situations
or
- someone else will write it, and then people who want to port their
postinstall scripts to IPS, will probably just use the wrapper, and ignore
the other ways to do it, because you've shown that you dont care about their
needs so why should they listen to you?
"My way or the highway", often leads to "the highway".
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
