In the case of pycompile the /usr/share/pkg/transforms/documentation could be a template for us. It contains postprocessing actuators for man-index, texinfo, etc.
On 08.01.16 10:08, Dagobert Michelsen <[email protected]> wrote: > > Hallo Carsten, > > Am 07.01.2016 um 12:04 schrieb Carsten Grzemba <[email protected]>: > > On 07.01.16 11:45, Dagobert Michelsen <[email protected]> wrote: > >> Am 07.01.2016 um 11:08 schrieb Carsten Grzemba <[email protected]>: > >> > 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 useful > >> > 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. > > > > But it is not so elegant if every Python package provide its own pycompile > > script with a own FB-SMF. > > True, I haven’t investigated the details for IPS in such cases, if you are > willing to > implement it I certainly won’t go against your educated decision. > > > 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 > >
