-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Johnny Hughes Sent: Thursday, May 19, 2005 8:48 AM To: CentOS ML Subject: Re: [CentOS] 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?
-- Marc
On Thu, 2005-05-19 at 08:52 -0500, Marc Powell wrote:
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Johnny Hughes Sent: Thursday, May 19, 2005 8:48 AM To: CentOS ML Subject: Re: [CentOS] 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 :)
On Thu, 2005-05-19 at 08:52, Marc Powell wrote:
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?
It shouldn't be a problem to add new modules via CPAN that the core rpms don't know about. It would be a problem to upgrade perl to a new version this way.
On Thu, May 19, 2005 at 08:52:56AM -0500, Marc Powell enlightened us:
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's one issue, the other is if there is ever a perl upgrade upstream, you'll have to figure out what modules were installed via CPAN and rebuild them. Admittedly that's not a huge problem, since upgrades to perl don't happen that often.
There are a couple of CPAN->RPM type programs out there. They're not perfect, but at least you can keep track of things in the RPM database that way.
Matt
-
Johnny Hughes -
Les Mikesell -
Marc Powell -
Matt Hyclak