On Thu, 2005-05-19 at 08:52 -0500, Marc Powell wrote:
>
> > -----Original Message-----
> > From: centos-bounces@xxxxxxxxxx [mailto:centos-bounces@xxxxxxxxxx] On
> > Behalf Of Johnny Hughes
> > Sent: Thursday, May 19, 2005 8:48 AM
> > To: CentOS ML
> > Subject: Re: web.vcs.u52.k12.me.us/linux/smbldap problems
> >
> > On Thu, 2005-05-19 at 09:41 -0400, Robert Moskowitz wrote:
> > > I am perhaps going about this the hard way of getting SAMBA all
> running
> > on
> > > my Centos 4 install...
> > >
> > > These scripts are set up to work with Fedora Core 3 or K12LTSP 4.2
> > >
> > > I got the install to work. It did not seem to hard.
> > >
> > > Then the docs tell me to install apt from Fedora project. Well I am
> > using
> > > yum so I ignore that.
> > >
> > > Next step is to run:
> > >
> > > perl -MCPAN -e -shell
>
>
> > >
> >
> > perl -MCPAN -e shell
> >
> >
> > (but using CPAN to update perl will break things)
>
> I use CPAN all the time and haven't had any problems. Are you saying
> this because yum/rpm wouldn't know they were installed? Can you expand
> on your concerns?
>
That is exactly the issue ... several programs install RPMS that contain
perl modules (and that are requirements). When you use CPAN, yum/rpm
don't know what is really installed. Packages that contain perl modules
over write what is installed via CPAN as well (without regard to CPANs
installs).
So you are left with a mess, in most cases.
One where perl modules can be very hard to track.
Having a perl module that is too old or too new can cause major issues.
Those are my concerns :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.centos.org/pipermail/centos/attachments/20050519/9539aabe/attachment.bin
