portmanager and perl threaded

[Michael C. Shultz]

On Wednesday 29 June 2005 00:38, you wrote:
> # ringworm01 at gmail.com / 2005-06-29 00:33:10 -0700:
> > On Wednesday 29 June 2005 00:26, you wrote:
> > > # ringworm01 at gmail.com / 2005-06-29 00:22:35 -0700:
> > > > On Wednesday 29 June 2005 00:03, Roman Neuhauser wrote:
> > > > > # ringworm01 at gmail.com / 2005-06-28 20:15:49 -0700:
> > > > > > On Tuesday 28 June 2005 19:20, Abu Khaled wrote:
> > > > > > > On 6/29/05, Michael C. Shultz <ringworm01 at 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.
> > > > >
> > > > >     The OP is asking about circumventing a bug in portmanager that
> > > > >     causes it to incorrectly think that lang/perl5.8 (5.8.7) built
> > > > >     -DWITH_THREADS, (PKGNAME "perl-threaded-5.8.7" because
> > > > >     PKGNAMESUFFIX=-threaded), is older than lang/perl5.8 (5.8.7)
> > > > > built without threads (PKGNAME "perl-5.8.7" because
> > > > > PKGNAMESUFFIX=).
> > > >
> > > > There isn't a bug in portmanager, it is building perl exactly how it
> > > > is told to "perl-5.8.7" where the old version is
> > > > "perl-threaded-5.8.7", it is up to the OP to set the build options
> > > > correctly.
> > >
> > >     How exactly is it old if the version number is the same?
> > >
> > >     Wait, you mean it thinks perl needs rebuilding because the options
> > >     are now different, which implies desire of change in the
> > >     administrator?  That would be a reasonable logic...
> >
> > Correct. I did make a mistake in the examples above though
> > lang/perl5|WITH_THREADS=yes| should be
> > lang/perl5.8|WITH_THREADS=yes|, I just sent him a message
> > with the correction.
>
>     BTW, you might want to bounce this to the mailing list so that the
>     thread there doesn't end in my lame assertion.

As you wish.

-M