#17074 closed defect (wontfix)
Correct autoconf perl dependency (again)
| Reported by: | michaelld (Michael Dickens) | Owned by: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.6.0 |
| Keywords: | autoconf, perl | Cc: | |
| Port: | autoconf |
Description
This was just corrected, but it doesn't provide the correct version of perl ... the current version requests the port 'perl5' instead of 'perl5.8' ... the latter is more up to date, and I think is what is desired since it is what older versions of autoconf required. This patch file changes the dependency to use port 'perl5.8'.
If the current behavior is desired, then it would be wise to update other ports that depend on 'perl5.8' to then use 'perl5' instead. As should be obvious, 'port' cannot have both perl ports installed at the same time, so please choose to use one or the other for all ports. Thanks! - MLD
Attachments (1)
Change History (6)
Changed 15 years ago by michaelld (Michael Dickens)
| Attachment: | autoconf-Portfile.diff added |
|---|
comment:1 Changed 15 years ago by jmroot (Joshua Root)
| Owner: | changed from macports-tickets@… to mcalhoun@… |
|---|
See #16830.
comment:2 Changed 15 years ago by michaelld (Michael Dickens)
Ah. So is "perl5" the new "perl5.8" and soon-to-be version 5.10 as well? In other words, should I be updating my MacPorts install of perl from "perl5.8" to "perl5", even though they conflict right now? I would have hoped that the slight change in the autoconf Portfile would not have made such a big deal ... that "perl5" and "perl5.8" would first have been revised so that they didn't conflict.
Oddly enough, this latest autoconf installed even without "perl5" being fully installed, probably because ${prefix}/bin/perl is already there (provided by "perl5.8").
Thanks for helping to straighten out the perl issue; I hope it comes smoothly and soon, so-as to avoid the issue this ticket is regarding - in other ports at least.
comment:3 Changed 15 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
I would recommend not switching to perl5 yet.
If a port depends on path:bin/perl:perl5.8 or path:bin/perl:perl5, then either perl5 or perl5.8 will satisfy the requirement (as with autoconf).
If a port depends on port:perl5.8, it will try to install perl5.8 and a conflict will arise if perl5 is installed.
There are still ports which depend on port:perl5.8.
I am working diligently to convert them to have path dependencies.
My intention was that the transition from perl5.8 to perl5 would be painless.
autoconf seems to have become a problem because of a bug in the way MacPorts interprets path dependencies.
Fortunately, there is an easy workaround.
As I mentioned in #16830, my plan is to eventually have perl5.8 not install ${prefix}/bin/perl and avoid a conflict with perl5.
I can not do this yet, however, because the perl PortGroup makes use of perl5.8.
A PortGroup revision will have to wait until the next MacPorts release (see #14553 for a discussion on this topic).
Since autoconf seems to be working for everyone again, I will close this ticket.
As it stands, autoconf is in keeping with the plan in #16830.
If you disagree, then you can reopen or contribute to the discussion in #16830.
My sincere hope is that, in the long run, perl5 will make perl maintenance easier.
In this case, the unpleasantness of the transition will be worth it.
comment:4 Changed 15 years ago by michaelld (Michael Dickens)
I'll let this ticket rest; it's in the archives for searching in case anyone else has this issue & wants to know what's going on. Good luck with the transition; I'm sure it will be worth it once all is said and done. - MLD
Patch to change autoconf Portfile to use perl5.8 insteaed of perl5.