On Jan 14, 2004, at 11:16 AM, Guay Jean-Sébastien wrote:
Which I interpreted as "without being forced to reinstall all my
modules
which are not part of the standard Perl distribution". So you confirm
that
that isn't possible, and that any modules that contain XS code and
which
were not part of
Hello drieux,
> the upgrade will upgrade and install the
> XS compatible for 5.8.X version of the code
> for all of the components that are in the RPM.
>
> any additional perl modules that have an XS component
> will need to be re-built and installed.
Exactly, that's what I was wondering about..
On Jan 14, 2004, at 10:33 AM, Guay Jean-Sébastien wrote:
This should allow you to do an upgrade rather then remove and upgrade.
If it's possible to do that (and have it actually work), does that
mean that
it's only on Windows (with ActiveState Perl) that Perl 5.6 and 5.8 are
not
binary compatibl
> This should allow you to do an upgrade rather then remove and upgrade.
If it's possible to do that (and have it actually work), does that mean that
it's only on Windows (with ActiveState Perl) that Perl 5.6 and 5.8 are not
binary compatible for XS modules? If not, I would think that simply
upgr
Have you tried:
rpm -ivh perl_rpm_name?
This should allow you to do an upgrade rather then remove and upgrade.
HTH.. Denis
On Tue, 13 Jan 2004, Paul Kraus wrote:
> On a Linux system how can I remove the 5.6 rpm and then install the 5.8.2
> from source and still maintain dependencies? If somet
On Jan 13, 2004, at 1:02 PM, Paul Kraus wrote:
On a Linux system how can I remove the 5.6 rpm and then install the
5.8.2
from source and still maintain dependencies? If something is looking
for
perl how do I make sure that it upgrades correctly?
This is probably a bit odd,
but why not skip the p
On a Linux system how can I remove the 5.6 rpm and then install the 5.8.2
from source and still maintain dependencies? If something is looking for
perl how do I make sure that it upgrades correctly?
Paul Kraus
---
PEL Supply Company
Network Administrator
--
