tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Perl5 update

Edgar Fuß <> writes:

> Shouldn't there be an infrastructure mechanism that allows a Perl Module's 
> Makefile to express either
>       I need Foo::Bar 47.11, and I assume it's in Core
> (which sets PKG_FAIL_REASON if that assertion is false)
> or better
>       I need Foo::Bar 47.11, take it from Core or devel/p5-Foo-Bar
> (adding a dependency on the latter if the former is false)?
> I don't think that would be too hard to implement. You need a pre-digested 
> corelist output in lang/perl5/somewhere, an fgrep and a version comparison.
> You could even automatically add a CONFLICTS+= p5-Foo-Bar if you take 
> Foo::Bar from Core. I guess Perl Module packages automatically depend on 
> "this Perl Version and not the next one", don't tey?

A big question is the cost/benefit of adding this flexibility.  In
general, one has to build from a consistent checkout of pkgsrc.  And
building packages with other packages being out of date gets one into
tricky territory.  So saying that p5-* packages in pkgsrc should expect
the current perl5 version seems like a simplifying assumption that saves
a lot of work, but on the other hand expects people to replace their
perl interpreter with the one from the pkgsrc version they are using.

Attachment: pgpaOjujEwMkp.pgp
Description: PGP signature

Home | Main Index | Thread Index | Old Index