cvs commit: ports/Mk bsd.port.mk ports/lang/perl5 Makefile ports/lang/perl5/files use.perl ports/lang/perl5.8 Makefile ports/lang/perl5.8/files use.perl

[David O'Brien]

On Fri, Feb 11, 2005 at 10:07:32AM +0100, Anton Berezin wrote:
> > I just did 'portupgrade perl-5.8.5' and wound up with 
> > 
> >     # added by use.perl 2005-02-11 00:18:00
> >     PERL_VER=5.8.6
> >     PERL_VERSION=5.8.6
> >                     
> > in my /etc/make.conf.  Can we please stop spamming /etc/make.conf with
> > this?  It is a source of very confusing bugs how it overrides
> > /usr/ports/Mk/bsd.*.mk for no good reason.
> 
> I believe that most of your concerns which you raised back in September
> are addressed now, unless I misinterpreted what those concerns were.  In
> particular, current versions of both lang/perl5 and lang/perl5.8 do not
> produce a stream of "added by use.perl" patches to /etc/make.conf, as it
> used to be, so the spamming is definitely less severe now.  As for the
> actual patching of /etc/make.conf, I remember you've mentioned that some
> people doing embedded work got confused by this.  Let me quote you:
> 
> 	I know some people using FreeBSD in appliances that have been very
> 	puzzled that their perl related changes in ports/Mk/bsd.port.mk
> 	would not take affect -- because they were unknowingly being
>     overridden by 'use.perl port's /etc/make.conf values.
> 
> I don't think this should be a concern.  For the majority of people the
> change in /etc/make.conf is needed.  Those who are modifying bsd.port.mk
> should know what they are doing more than most.

At this point I don't see why this is needed there is no base perl.  Why
doesn't the Python or ruby ports need to override _PYTHON_VERSION or
RUBY_VERSION in /etc/make.conf?  What makes Perl so special on a 5.3 or
6-CURRENT system?

-- 
-- David  (obrien at FreeBSD.org)