Opened 10 years ago

Closed 8 years ago

#42581 closed defect (fixed)

stow @2.2.0_0 Bad installation path for perl module

Reported by: fh@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: cooljeanius (Eric Gallager), fracai, mojca (Mojca Miklavec), dbevans (David B. Evans)
Port: stow

Description

The stow port depends on perl 5.16 but has perl module installed for perl 5.12.4.

$ port rdeps stow
The following ports are dependencies of stow @2.2.0_0:
  perl5
    perl5.16
      gdbm
        gettext
          expat
          libiconv
            gperf
          ncurses
$ port contents stow
...
  ${prefix}/lib/perl5/site_perl/5.12.4/Stow.pm
  ${prefix}/lib/perl5/site_perl/5.12.4/Stow/Util.pm
...

Change History (8)

comment:1 Changed 10 years ago by cooljeanius (Eric Gallager)

Cc: egall@… added

Cc Me!

comment:2 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

What version of perl stow installs itself for depends on what variant of the perl5 port you have installed. That needs to stop. For example, we could add variants to the stow port so the user can select what version of perl they want to use.

comment:3 Changed 10 years ago by fracai

Cc: arno@… added

Cc Me!

comment:4 Changed 10 years ago by fracai

The biggest headache here is that the binary archive at http://packages.macports.org/stow installs for perl5.12. Passing "-s" will disable binary archives if you need stow with a different perl before this is fixed.

comment:5 in reply to:  4 Changed 10 years ago by fh@…

Replying to arno@…:

The biggest headache here is that the binary archive at http://packages.macports.org/stow installs for perl5.12. Passing "-s" will disable binary archives if you need stow with a different perl before this is fixed.

Thanks! I am used to only install from source, and I did not noticed that I installed the binary archive this time. That would probably be better to not provide any binary archive till the problem is cleanly solved (stow takes a few seconds to install from sources)

comment:6 Changed 8 years ago by mojca (Mojca Miklavec)

Cc: mojca@… devans@… added
Version: 2.2.1

I committed r144204 / r144205, but there were a few earlier commits that should have fixed the problem. Is this still a problem for anyone or may I close the ticket?

(We could add variants if needed. Does anyone need to access the modules from outside of the stow executable?)

Last edited 8 years ago by mojca (Mojca Miklavec) (previous) (diff)

comment:7 Changed 8 years ago by mojca (Mojca Miklavec)

I'm closing the ticket. I would think that r118138 must have fixed the problem already. If there are still problems, please reopen the ticket or open a new one.

comment:8 Changed 8 years ago by mojca (Mojca Miklavec)

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.