On Tue, 24 Aug 2004 08:23, Jeff Johnson <n3npq@xxxxxxxxx> wrote:
> On a parallel, multilib install battle front, /usr/bin/{glibc,libgcc}
> have also been causing rpm pain.
>
> The packaging requirements are that these packages must be installable
> into an empty
> chroot, i.e. no /bin/sh, hence statically linked helpers.
>
> Unfortunately, the statically linked helpers are installed on the same
> path, but are
> platform dependent. The statically linked helpers are also quite
> mysterious, e.g.
> this isn't the first time that the rpm_t vs. rpm_script_t has been raised.
>
> One approach to a multilib packaging solution is to use embedded lua to
> avoid platform
> dependent helpers that are on conflicting paths.
>
> But that then means that embedded lua will be run as "rpm_t", not
> "rpm_script_t",
> as this is rpm running in a nearly empty chroot.
The main use for chroot operation of RPM is for the early stages of the
install process. Currently we don't do this in enforcing mode so this
doesn't matter.
What is a LUA?
I suggest using /bin/sh to execute the postinst commands if it exists. If
there is no /bin/sh then just execute them directly and don't worry about SE
Linux.
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
