Date: Wed, 29 Jun 2005 10:00:44 +0300 From: Abu Khaled <khaled.abu@gmail.com> To: "Michael C. Shultz" <ringworm01@gmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: portmanager and perl threaded Message-ID: <a64c109e05062900005f30bc0d@mail.gmail.com> In-Reply-To: <200506282015.50439.ringworm01@gmail.com> References: <a64c109e0506281800a2634c8@mail.gmail.com> <200506281911.13454.ringworm01@gmail.com> <a64c109e05062819207c5e24a6@mail.gmail.com> <200506282015.50439.ringworm01@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 wan=
ted
> > > > 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 opt=
ion.
> > >
> > > -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=3Dyes".
>=20
> I'm not an expert on the perl port so may misunsterstand your question, i=
f so
> sorry. If your asking what I think your are though, all you have to do i=
s
> make an entry like this:
>=20
> lang/perl5|WITH_THREADS=3Dyes|
>=20
> in /usr/local/etc/portmanager/pm-020.conf then portmanager will always
> build perl with that setting.
>=20
> >
> > 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.
>=20
> Is it possible you have the WITH_THREADS=3Dyes set in portupgrade's
> config file but not portmanager's? Another option so you don't have to s=
et
> this in two files is to put it in /etc/make.conf then it will apply no ma=
tter
> how the port is upgraded, the line would look like this:
>=20
> .if ${.CURDIR:M*/lang/perl5}
> WITH_THREADS=3Dyes
> .endif
>=20
> -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.
--=20
Kind regards
Abu Khaled
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a64c109e05062900005f30bc0d>