What's the right @INC path?

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

 



Hello all,

there were recently some bugs considering the @INC path.
(For the curious: bugs 448735 and 452898.)

The current @INC contains long directory names.  (I visited a Debian
machine and it looked much saner.)
I would like to understand the reasons.

Let's imagine that @INC would be the following:

/usr/lib/perl5/5.10.0	-Darchlib=%{_libdir}/perl5/%{perl_version}
/usr/share/perl5/5.10.0	-Dprivlib=%{_prefix}/share/perl5/%{perl_version}
/usr/local/lib/perl5	-Dsitearch=%{_prefix}/local/%{_lib}/perl5
/usr/local/share/perl5	-Dsitelib=%{_prefix}/local/share/perl5
/usr/lib/perl5		-Dvendorarch=%{_libdir}/perl5
/usr/share/perl5	-Dvendorlib=%{_prefix}/share/perl5

What would be wrong if we switched to this simple layout?

More exactly:
First, what would be wrong with this setup if it were used in a fresh new
distribution?
And when the answer for the above is "nothing", then more
questions come: Is it feasible to get to that setup in F-10?  Which
backward compatibility provisions should be done in order to ease the
transition for Fedora users?

Thank you in advance for any explanations,
	Stepan Kasal

--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Fedora-perl-devel-list mailing list
Fedora-perl-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-perl-devel-list

[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Legacy Announce]     [Fedora PHP Devel]     [Kernel Devel]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Big List of Linux Books]     [Gimp]     [Yosemite Information]
  Powered by Linux