[indiana-discuss] "no scripting zone" and isaexec(3C) == architectural problem

[Moinak Ghosh]

On Wed, Jun 3, 2009 at 6:54 PM, UNIX admin <tripivceta at hotmail.com> wrote:
> My problem is simple:
>
> I want to deliver both 32- and 64-bit binary payload in my packages. In order for the system to run the correct binary, I use isaexec(3C).
>
> The problems start with the fact that I adhere strictly to the filesystem(5) manual page, respectively the System V filesystem specification. Since my payload falls under "3rd party and unbundled applications", it goes into /opt, and /etc/opt, and /var/opt, as per spec.
>
> Now, since /opt can be a separate filesystem, and isaexec does not work/operate with soft links, I'm forced to bundle my own copy of isaexec in /opt/abcd/lib/isaexec.
>
> A better but not perfect solution would be to copy /usr/lib/isaexec into /opt/abcd/lib/, but the IPS packaging system does not provide the "postinstall" facility, since it is a "no scripting zone".
>
> Between isaexec working only with hard links and IPS not providing any way to execute scripts at installation time, do any of you have any suggestions how to solve this architectural problem?

   One solution is to create a little program that utilizes the
   isaexec API and accepts a pathname to an executable.
   See  isaexec(3C).

Regards,
Moinak.
-- 
================================
http://www.belenix.org/
http://moinakg.wordpress.com/