Date: Wed, 29 Jun 2005 05:20:07 +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: <a64c109e05062819207c5e24a6@mail.gmail.com> In-Reply-To: <200506281911.13454.ringworm01@gmail.com> References: <a64c109e0506281800a2634c8@mail.gmail.com> <200506281911.13454.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 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/per= l5.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? >=20 > Its covered in the man page. see the -ip option, or the conf file option. >=20 > -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". 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 Kind regards Abu Khaled
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a64c109e05062819207c5e24a6>