[gobolinux-devel] Perl modules directories
Michael Homer
michael at gobolinux.org
Fri Mar 14 10:26:34 NZDT 2008
On Fri, Mar 14, 2008 at 2:02 AM, Jonas Karlsson <jonka750 at student.liu.se> wrote:
> Getting svk to play nicely forced me to revise things with how Perl
> was configured. I was annoyed about having to rebuild my modules every
> time I made a bugfix upgrade of perl as well. For example sitelib for
> Perl 5.8.8 was configured as $target/lib/perl5/site_lib/5.8.8, but
> first I wanted to change it to point at /S/L/L, which was no problem,
> but is it ok to drop $version for the path, e.g. setting sitelib to
> $goboLibraries/perl5/site_lib? How is binary compability between minor
> releases, 5.8 -> 5.10 for modules?
There is no binary compatibility, and there isn't necessarily source
compatibility (new keywords, etc). It's probably reasonably safe to
do, so long as there's awareness that binaries may need recompilation
after an upgrade. Reinstalling source modules shouldn't be necessary
except in very rare cases.
Not using svk wouldn't really address the root issue here. We still
need to have it available if someone does want it, and it's exposing a
lower-level problem.
-Michael
More information about the gobolinux-devel
mailing list