the future of cswclassutils in IPS

[Dagobert Michelsen]

Hi Carsten,

Am 07.01.2016 um 11:08 schrieb Carsten Grzemba <grzemba at contac-dt.de>:
> for IPS packages we have to do some rework related postinstall/preremove and the class action utils.
> Some issues can handle IPS itself, e.g. create user group, preserve configuration. Other we have to rewrite.
> Should we keep the cswclassutil package with scripts are still usefull but install the scripts in a new /opt/csw location.
> Or should we create for every script an own package.
> One example would be cswpycompile. This script/package would be a dependency for every Python package and on install package it has to trigger a SMF for compiling.

I tend to remove the dependency to CSWcswclassutils and include whats needed in the package.


Best regards

  — Dago

--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20160107/be2429ba/attachment.asc>