Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 23 Sep 2005 07:39:30 -0500
From:      Greg Barniskis <nalists@scls.lib.wi.us>
To:        Peter Clutton <peterclutton@gmail.com>
Cc:        David Armour <dfarmour@myrealbox.com>, freebsd-questions@freebsd.org
Subject:   Re: NEWBIE: how-to for feeding file to gnomealyzer.sh?
Message-ID:  <4333F782.3080004@scls.lib.wi.us>
In-Reply-To: <57416b30050922232617728fd@mail.gmail.com>
References:  <200509212203.35549.dfarmour@myrealbox.com>	<57416b300509222218697a524b@mail.gmail.com>	<43339EC3.8040605@altern.org> <57416b30050922232617728fd@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Peter Clutton wrote:
> On 9/23/05, Gregory Nou <gregorynou@altern.org> wrote:
> 
>>You should install port textproc/p5-XML-Parser, and if already
>>installed, verify that the link are well done in your /usr/local/bin (eg
>>: not something like using perl5.8 and having perl pointing on perl5.6.2)
> 
> 
>  Thanks for that. I usually check out the port it mentions in it's output,
> but the XML-parser thing threw me. Will have a look tonight and let you
> know.

In a couple of cases where I had issues like this with gnome 
installation (and the XML-Parser thing sounds awfully familiar), I 
think I found that it was most efficient to do something like:

portupgrade [args] perl
perl-after-upgrade
portupgrade <everything but gnome, esp. xorg stuff>

Then the gnome install would run just swell. This was several months 
ago, so my memory could be a bit fuzzy on this.

I think the gnome FAQ indicates one should just "portupgrade -a" 
first, but of course that doesn't always work out well since -a 
includes gnome if already installed. Success with gnome very much 
depends on other things being up to date though. Modify to suit your 
port management habits.

Note that my recipe will have you using perl5.8 during the gnome 
upgrade. The tip on using 5.6.2 instead might be another way around, 
but I'm pretty sure the root of the problems I had were actually 
with imake and maybe other X stuff not being in the state required, 
even though the evident choke symptom is on a perl module.

-- 
Greg Barniskis, Computer Systems Integrator
South Central Library System (SCLS)
Library Interchange Network (LINK)
<gregb at scls.lib.wi.us>, (608) 266-6348



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4333F782.3080004>