[Pkg-team] IPS packages and perl modules
lundman at lundman.net
Thu Dec 1 07:34:40 UTC 2011
I have proceeded with 1) as it seemed to make most sense.
Alas, I made some assumptions. oi is all 64bit, including the perl binary itself
(hurrah), so we thought maybe we can drop 32bit entirely.
But alas, all perl MODULES are 32bit, and it can not load 64bit modules. So,
modules have to be 32bit, and anything they link with, say BerkeleyDB, also
needs to be 32bit, but the OS wants 64bit.
Ick. Just because of perl, we have to have mixed architectures, _still_.
Jorgen Lundman wrote:
> Hello list,
> We have started looking at making own IPS packages, with own repository, and
> having excellent progress. Everything is coming together nicely, but I have one
> One of the packages that I am making, requires a score of perl modules to be
> part of the dependencies.
> Now, "pkgdepend generate" appears not to "handle" perl modules (it sets a
> dependency on perl, but not any modules). Not that most modules are in the
> oi-repository anyway.
> My guess would be that I should use one of:
> 1) Somehow use CPAN to install modules in my $install_root directory that I
> build to make a package
> 2) Since there is no postinstall script, make a SMF service which runs once,
> installs the required modules, then removes itself.
> 3) Tell the admin to get his own damned modules after installing the package.
> Or is there a better way? Since SMF has special hooks in "pkg" utilities, does
> perl modules do as well (which executes cpan?)
Jorgen Lundman | <lundman at lundman.net>
Unix Administrator | +81 (0)3 -5456-2687 ext 1017 (work)
Shibuya-ku, Tokyo | +81 (0)90-5578-8500 (cell)
Japan | +81 (0)3 -3375-1767 (home)
More information about the Pkg-team