perl-after-upgrade does not process anything

Michael Nottebrock lofi at
Tue Jun 28 14:33:56 GMT 2005

On Tuesday, 28. June 2005 16:10, Jiawei Ye wrote:
> On 6/28/05, Florent Thoumie <flz at> wrote:
> >        The idea is "don't use portupgrade -a". Sure "portupgrade
> >        perl5.8" does the trick.
> >
> > --
> > Florent Thoumie
> > flz at
> Why? 'portupgrade -a' does not fix the perl dependancy, which is why
> we need the script in UPDATING in the first place, ie. no
> perl-depending port will be re-installed by portupgrade -a.

After an update of perl, portupgrade -a is normally bound to fail anyway - at 
least if there are other perl ports left to update, since dependency files of 
other perl-ports will be looked after in the new versioned directory, won't 
be found, will then be rebuilt and at installation time the update process 
will fail because the package is already installed (but the files are still 
in the old perl subdirectory).

At that point at the latest, you'd normally run perl-after-upgrade.

It might very well be however that perl-after-upgrade is confused by your perl 
package being registered as perl-threaded.

   ,_,   | Michael Nottebrock               | lofi at
 (/^ ^\) | FreeBSD - The Power to Serve     |
   \u/   | K Desktop Environment on FreeBSD |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url :

More information about the freebsd-ports mailing list