Hello,

I'm preparing a port for a Perl based monitoring system. The user part contains only Perl programs and a binary compiled elsewhere, that is - the port is only there to make a package from
the supplied files.
As for now, the port is not ready for distribution - that is, until I'll resolve updates mechanism and/or setup a public repository. Currently I'm using a port infrastructure to 'make package' and distribute the
resulting package outside of the official repositories.

The install process involves generating a PLIST from a fetched and extracted sources supplied with some additional tasks, like adding users and rc.scripts. But the install process requires some more complex operations, involving sed, awk and such. This could be put in PLIST in @exec-* and @unexec-* lines, but it
would be much easier to have pkg-install ability.
Currently it is done by adding install and deinstall scripts the target directory and running it from there. Alas, that's not the cleanest way - I don't want to pollute target tree with unnecessary scripts. I've tried some tricks, but didn't succeed in attaching any scripts to the package made from ports.

So, is it allowed in OpenBSD for the packages to have self-contained install/deinstall scripts (like pkg-install in FreeBSD) and if so, how do I do that? (I've been through Porter's Handbook but to no avail), if not - what's the OpenBSD's way to handle a situation when a package needs to run some complex
post-install script?

Best regards,
ML

Reply via email to