Date: Wed, 29 Jun 2005 00:28:07 -0700 From: "Michael C. Shultz" <ringworm01@gmail.com> To: Abu Khaled <khaled.abu@gmail.com>, freebsd-ports@freebsd.org Subject: Re: portmanager and perl threaded Message-ID: <200506290028.08503.ringworm01@gmail.com> In-Reply-To: <a64c109e05062900005f30bc0d@mail.gmail.com> References: <a64c109e0506281800a2634c8@mail.gmail.com> <200506282015.50439.ringworm01@gmail.com> <a64c109e05062900005f30bc0d@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 29 June 2005 00:00, Abu Khaled wrote:
> On 6/29/05, Michael C. Shultz <ringworm01@gmail.com> wrote:
> > On Tuesday 28 June 2005 19:20, Abu Khaled wrote:
> > > On 6/29/05, Michael C. Shultz <ringworm01@gmail.com> wrote:
> > > > On Tuesday 28 June 2005 18:00, Abu Khaled wrote:
> > > > > I have a situation here where portmanager treats
> > > > > perl-threaded-5.8.7 as an old port and tries to update it.
> > > > >
> > > > > -snip
> > > > > have:perl-threaded-5.8.7 status: OLD available:perl-5.8.7
> > > > > /lang/perl5.8 -snip
> > > > >
> > > > > Portmanager almost recompiled my entire ports tree and I was lucky
> > > > > to stop it before it uninstalled perl-threaded-5.8.7
> > > > > Portupgrade correctly reports that the port is up-to-date but I
> > > > > wanted to test portmanager and see how it differs from portupgrade.
> > > > > Can someone give me a workaround for this problem? What options do
> > > > > I need to add for portmanager configuration aside from IGNORE?
> > > >
> > > > Its covered in the man page. see the -ip option, or the conf file
> > > > option.
> > > >
> > > > -Mike
> > >
> > > Thanks Mike, but I want to know if there is a way to make portmanager
> > > recognize the port as current. perl-threaded-5.8.7 is the same port as
> > > perl-5.8.7 built with option "WITH_THREADS=yes".
> >
> > I'm not an expert on the perl port so may misunsterstand your question,
> > if so sorry. If your asking what I think your are though, all you have
> > to do is make an entry like this:
> >
> > lang/perl5|WITH_THREADS=yes|
> >
> > in /usr/local/etc/portmanager/pm-020.conf then portmanager will always
> > build perl with that setting.
> >
> > > It's just seems strange why portupgrade considers the port current
> > > while portmanager refers to it as old. As I sait it is the same port
> > > but with a suffix and a build option.
> >
> > Is it possible you have the WITH_THREADS=yes set in portupgrade's
> > config file but not portmanager's? Another option so you don't have to
> > set this in two files is to put it in /etc/make.conf then it will apply
> > no matter how the port is upgraded, the line would look like this:
> >
> > .if ${.CURDIR:M*/lang/perl5}
> > WITH_THREADS=yes
> > .endif
> >
> > -Mike
>
> I added the compile option to pm-020.conf but still portmanager treats
> the port as OLD and wants to update. So the problem is still there
> portmanager does not consider perl-threaded-5.8.7 and perl 5.8.7 to be
> the same port. Portupgrade on the other hand sees it as the same port
> and does not update it.
>
> Well I guess that all I have left is to IGNORE the port in pm-020.conf.
I messed up in the above examples, they are not for perl5.8, they should be as
follows:
.if ${.CURDIR:M*/lang/perl5.8}
WITH_THREADS=yes
.endif
lang/perl5.8|WITH_THREADS=yes|
-Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200506290028.08503.ringworm01>