> These messages? OK, clarifying: There are 2 issues here. First line: You
> need the Config::IniFiles perl module. The whole cpan2rpm / cpanflute2
issue
> has been discussed recently here.
I found the discussion thread I believe you are referring to. I joined the
list after that discussion had taken place. Has anyone realised that the
mailing list archives are not sorted by date/time? So as suggested in that
thread I used apt-get to download and install cpanflute2 (apt-get is such a
wonderful little tool that just seems to simply work).
# apt-get install perl-RPM-Specfile
Ok, this installed cpanflute2 without any fuss at all. Next I had to find
out what CPAN was. Why is so much knowledge simply assumed of the newcomer
when it comes to Linux? Found it at http://www.cpan.org and downloaded the
stable release of perl as the site strongly recommended (stable.tar.gz).
Next I tried to build the RPMs as per the cpanflute2 discussion thread.
# cpanflute2 --buildall stable.tar.gz
Besides the warning that compression is not available, it complained that it
could not parse the module or version name from the filename. Ok, so I go
through a few more hoops at CPAN and find perl-5.8.0.tar.gz, download it and
try again.
# cpanflute2 --buildall perl-5.8.0.tar.gz
This results in the process starting, but then it falls over with
+ perl Makefile.PL PREFIX=/var/tmp/perl-perl-5.8.0-8-root/usr
Can't open perl script "Makefile.PL": No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.15550 (%build)
Now I have no idea of where to go or what to do again. Any hints?
> All the rest of the lines are saying that the upgrade of apache you are
> trying to install is incompatible with your installed mod_perl, mod_python
> and php packages. You may be able to simple uninstall those packages. If
you
> need to use them, you will need to locate or build versions compatible
with
> the new apache version.
Uninstalling mod_perl, mod_php and mod_python removed those dependency
errors. Hopefully the system will still work without those modules. Now I
just have to get Perl updated.
> > It seems to be a lot of hacking and manual labour just to get Subversion
> > updated on RH9. This is a large (insurmountable) barrier to newcomers.
>
> This is really RPM standard operating procedure. If it is a barrier, it
> isn't one erected by Subversion. It's also a vital skill for working with
> Red Hat and similar distros.
I'm not implying that the barriers are caused by Subversion. It is RPM that
seems to be raising them. The only joy I have found so far is apt-get for
RH9. Everyting I have asked of it has simply worked so far. With the
standard operating procedure for RPM being so difficult for newcomers, I am
very surprised that apt-get has not been more widely accepted by the Red Hat
community.
> > I'm getting more tempted to pay for a new WinXP license. I know it's
> going to
> > work there with no dependency issues.
>
> Overreacting...
At this stage after hitting so many barriers, I don't think it is
overreacting at all. How many other people have tried to install Subversion
0.24.2 or 0.25.0 on a fresh installation of RH9? Surely I'm not the only
one to have all these issues. I am noting down every hoop I've had to jump
through into a complete idiot's guide to installing Subversion 0.25.0 on Red
Hat 9, if not only to serve as a guide for myself if I have to go through
this again in the future.
Sly
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 14 12:23:47 2003