[oi-dev] updating the perl stack on hipster

[Tim Mooney]

In regard to: Re: [oi-dev] updating the perl stack on hipster, Alexander...:

> 1) perl sun_solaris module is provided by illumos-gate. illumos-gate is currently built with Perl 5.22.  The tricky issue is that to build illumos-gate with Perl 5.30 you need Perl 5.30 sun_solaris modules. The following sequence usually worked:
> Compile illumos-gate with Perl 5.30. First build fails, but produces necessary modules. Copy them to the build server. Rebuild illumos-gate.
> OI-userland component was used to provide modules for perl version different from one used to build illumos-gate and now is not used.

Ok, thanks for that explanation, Alexander.  That explains much of what
was confusing me about the sun_solaris module.

> 2) I think the plan should look like this.
> - Deliver Perl 5.30.
> - Deliver Perl 5.30 modules.

Those first two steps should be "easy", I'll continue working on them and
start submitting PRs when I'm ready.

> - Check what dependencies on Perl 5.22 we have, especially depenencies on libraries (net-snmp? PostgreSQL?) and try to rebuilt it with Perl 5.30. Can be tricky, given that Perl 5.22 was 32-bit. Perhaps, will have to drop some 32-bit binaries/libraries.

Understood.  I'll plan on looking at that once I'm close to done with the
modules.

> - Switch illumos-gate to Perl 5.30.

Up to now I've only contributed to oi-userland, so when we get this far,
I'll ask for some help.  It will be a while before then.

Thanks for the info!  Much appreciated.

Tim

> ________________________________________
> От: Tim Mooney <Tim.Mooney at ndsu.edu>
> Отправлено: 4 января 2020 г. 1:07
> Кому: oi-dev at openindiana.org
> Тема: [oi-dev] updating the perl stack on hipster
>
>
> I would like to get both the perl runtime and the collection of perl
> modules we ship updated to something recent.
>
> I have packages for runtime/perl-530 (5.30.1) and several of our easiest
> modules (those with no additional module dependencies) built for that
> runtime.  Before I move on to the more difficult modules, I want to make
> certain I'm on the right track.
>
> I have several questions about the sun-solaris perl module collection, and
> I'm hoping someone has some guidance.
>
> - this is the only perl module we ship that is in the
>
>        /runtime/perl-NNN/module/sun-solaris
>
> namespace, rather than
>
>        /library/perl-5/sun-solaris-NNN
>
>   Anyone know why it's in the /runtime namespace, rather than the
>   /library namespace?  I'm trying to understand why it's an
>   exception that doesn't match any of the other module naming conventions.
>
> - The component we currently ship (runtime/perl-522/module/sun-solaris)
>   was not generated from the current oi-userland/perl/sun-solaris sources.
>   The files in that directory are still set to perl-516 and the packaged
>   component includes PerlGcc and Exacct, both of which appear to have
>   been dropped from runtime/perl-522/module/sun-solaris.
>
>   Was the source code moved somewhere else (I've looked and haven't found
>   it) or were the changes that built runtime/perl-522/module/sun-solaris
>   perhaps never committed?
>
> I'm mainly trying to determine whether I should include Exacct when I
> update the sun-solaris module, or drop it as the perl-522 has apparently
> done.  PerlGcc should definitely be dropped.
>
> - once I have sun-solaris and remaining modules packaged for perl-530,
>   what's the easiest method (from the perspective of the core developers)
>   to proceed?
>
>     - a "meta" pull request, that references each individual pull request?
>        - make 530 and modules available before obsoleting/removing perl-524?
>        - how do we go about eventually getting rid of perl-522?
>
> I know that long-term we don't want to be providing 3 versions of perl,
> I'm just not certain what the transition process should look like.
>
> Tim
> --
> Tim Mooney                                             Tim.Mooney at ndsu.edu
> Enterprise Computing & Infrastructure /
> Division of Information Technology    /                701-231-1076 (Voice)
> North Dakota State University, Fargo, ND 58105-5164
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> https://openindiana.org/mailman/listinfo/oi-dev
>

-- 
Tim Mooney                                             Tim.Mooney at ndsu.edu
Enterprise Computing & Infrastructure /
Division of Information Technology    /                701-231-1076 (Voice)
North Dakota State University, Fargo, ND 58105-5164