So how about installing this limited number of perl modules into some
'new' directory (outside of @INC) and having a 'perl-rpmforge-
activator' RPM which basically would just prepend this new directory
to @INC ? This way it would be pretty easy to activate and de-active
these modules, there would be no conflicting files etc.
Dominik
On 17-Sep-08, at 6:14 PM, Dag Wieers wrote:
On Wed, 17 Sep 2008, Dave Cross wrote:
Dag Wieers wrote:
That is why I think we need to somehow make Red Hat understand that
they should not add CPAN distributions to the perl package.
It's not Red Hat that does this. The standard Perl distribution
contains
modules that are also distributed independently from CPAN. They are
known as "dual-life" modules.
Right. But the fact that they are part of the perl RPM and not
packaged as seperate RPMs makes it hard to replace them. Nothing
forces Red Hat to ship them with the perl RPM.
In the past I thought it was because Red Hat did not want those
modules to be replaced (given they have to support the system) and
the default module path ctually confirmed that.
But since RHEL5 they allow to replace modules from site_perl because
they changed the order, so there goes the bit of reverse
psychology :) So I would have expected them to package them
seperately so that at least it is more obvious from the package
database that a certain RPM was in fact replaced.
--
-- dag wieers, [EMAIL PROTECTED], http://dag.wieers.com/ --
[Any errors in spelling, tact or fact are transmission errors]
_______________________________________________
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
_______________________________________________
suggest mailing list
suggest@lists.rpmforge.net
http://lists.rpmforge.net/mailman/listinfo/suggest
