> The main reason for doing that sort of thing with most unixoid systems
> is that using a unique prefix for every software package you install
> means that you can easily identify which files belong to what package
> when later on it comes time to update things.
I understand this, but I still li
On Thu, Dec 11, 2003 at 09:56:27AM -0800, Tony Jones wrote:
>
> > > why is it in /usr/local/perl/bin? As far as I have seen, the ports
> > > collection doesn't do that. did you install as a port (make install in
> > > /usr/ports/lang/perl5.8)?
> >
> > Yes. make install PREFIX=/usr/local/perl
On Dec 11, 2003, at 9:54 AM, Tony Jones wrote:
I'm very unfamiliar with the ports system. I've never heard of
portinstall
or portupgrade.
Just running make && make install in the appropriate port subdirectory.
It seems to me you're making this really complicated: I don't know what
difference
> > why is it in /usr/local/perl/bin? As far as I have seen, the ports
> > collection doesn't do that. did you install as a port (make install in
> > /usr/ports/lang/perl5.8)?
>
> Yes. make install PREFIX=/usr/local/perl
I of course also did 'make PREFIX=/usr/local/perl' before doing the ins
> why is it in /usr/local/perl/bin? As far as I have seen, the ports
> collection doesn't do that. did you install as a port (make install in
> /usr/ports/lang/perl5.8)?
Yes. make install PREFIX=/usr/local/perl
Is that bad? I like to have large packages installed into seperate
sub-directorie
On Dec 10, 2003, at 8:34 PM, Tony Jones wrote:
At this point, /usr/local/perl/bin/perl is installed
why is it in /usr/local/perl/bin? As far as I have seen, the ports
collection doesn't do that. did you install as a port (make install in
/usr/ports/lang/perl5.8)?
What would happen if you were t
> Install Perl 5.8.2 from ports (or source)
I did this (/usr/ports/lang/perl5.8).
Made fine, but grokked during 'make install':
/bin/mkdir -p /usr/local/perl/lib/perl5/5.8.2/BSDPAN/ExtUtils
install -c -o root -g wheel -m 444
/usr/ports/lang/perl5.8/work/BSDPAN-5.8.0/ExtUtils/MM_Unix.pm
/usr/
The ports collection is great for certain things. I do happen to use
it for spam assassin on 4.9 Stable. I have perl 5.8.2 installed from
ports and I used use.perl to set it up as default.
Here is the problem with ports, many maintainers are using 5.x now.
Since there is only one ports colle
> [ snip ]
>
> I did suggest a very quick, easy and effective fix. It would have taken
> you less than two hours to download, build and configure perl and multiple
> CPAN modules [1] and been on your way.
Nick. I did all of what I said *BEFORE* you e-mailed your (excellent)
suggestion. I wi
On Tue, 09 Dec 2003 17:11:10 -0800, Tony Jones <[EMAIL PROTECTED]> wrote:
Hi Nick.
Thanks for the reply.
I already knew of the FreeBSD stock perl issues and was aware that
under no circumstances should I try to upgrade the stock Perl, but
I appreciate the reminded nontheless!!
I gave up on tryin
Hi Nick.
Thanks for the reply.
I already knew of the FreeBSD stock perl issues and was aware that
under no circumstances should I try to upgrade the stock Perl, but
I appreciate the reminded nontheless!!
I gave up on trying to install the SpamAssassin I obtained manually
from spamassassin.org a
On Mon, 08 Dec 2003 22:29:26 -0800, Tony Jones <[EMAIL PROTECTED]> wrote:
[ snip ]
So, this not working, I went and grabbed the sources for
Mail-SpamAssassin-2.60
and figured I'd try building it manually.
trying: perl -MCPAN -e shell (which is the INSTALL files recommended
way)
just generated
On Mon, 8 Dec 2003, Tony Jones wrote:
> Hi.
>
> Over time I've got into the habit of either using packages or building
> directly from the source. Last time I tried this (Postfix) and asked a Q
> here, I was rapped over the knuckles :-) and told to use the Ports.
>
> Right now I'm trying to build
Hi Tony,
I would use cvsup to update your ports tree.
You can use %make buildworld, to reinstall system
perl. Look in /etc/make.conf for NOPERL var to
unset accordingly to if you want to build it
or not.
You can also try to install perl from ports. Then
you can use %use.perl ports, or %use.per
Hi.
Over time I've got into the habit of either using packages or building
directly from the source. Last time I tried this (Postfix) and asked a Q
here, I was rapped over the knuckles :-) and told to use the Ports.
Right now I'm trying to build spamassassin, so I decided I'd be good and do
15 matches
Mail list logo
