Opened 9 years ago
Last modified 8 years ago
#50689 new submission
apl 1.5 Add new port GNU APL 1.5
Reported by: | txm.fourier@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | kurthindenburg (Kurt Hindenburg) | |
Port: | apl |
Description
Here is the new port GNU APL.
Attachments (3)
Change History (13)
Changed 9 years ago by txm.fourier@…
Attachment: | patch-src-native-file_io.cc.diff added |
---|
comment:1 Changed 9 years ago by txm.fourier@…
- Category: lang
- Tested on OSX 10.10.5, XCode Version 7.0 (7A220)
comment:2 Changed 9 years ago by mf2k (Frank Schima)
Keywords: | lang removed |
---|---|
Version: | 2.3.4 |
comment:3 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Why does it require gcc49? Does no other compiler work?
comment:4 Changed 9 years ago by txm.fourier@…
I've tried with 5.3.0 initially, got compilation errors about unknown '-rdynamic' argument. Switching to 4.9 solved the problem.
Changed 9 years ago by txm.fourier@…
Attachment: | patch-src-buildtag.diff added |
---|
Patch to use old svn to get revision info
comment:5 Changed 9 years ago by txm.fourier@…
I've updated Portfile to use SVN version instead of frozen 1.5, since the Author recommended to use this version.
The attached file patch-src-native-file_io.cc.diff should be removed, I've added another patch for the SVN version.
The SVN version doesn't need the gcc49 to compile.
I also volunteer to support this port.
comment:6 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
We would prefer not to fetch from revision control systems. We would rather use a tarball, and if a few patchfiles are needed to make it work right, cherry-picked from future commits, we can add those. If there are so many patches needed that patchfiles become impractical, it would be appropriate for the developer to release a new version of the software incorporating all the needed changes.
Why patch buildtag to use /usr/bin/svn and /usr/bin/svnversion instead of svn and svnversion? What problem do you encounter when using the MacPorts versions of svn and svnversion?
comment:7 Changed 9 years ago by txm.fourier@…
I know about SVN. The problem is what the author is not making releases ofter (in fact really really seldom, since it is one person project, and the previous version was in March 2015). He recommended to use latest from SVN as often as possible, that is why I decided to create this port from SVN. In any case it is a fixed revision, and I'm planning to upgrade revision not really often as well(not like once a week, rather once a month-two).
The patch was because svn checkout happened using /usr/bin/svn(Macports constructed command line using this version of svn, regardless of what I have installed svn from Macports), which is quite old, but svnversion in the GNU APL called without specifying the path(and in my system /opt/local/bin goes before /usr/bin), and therefore newer than the client checkout.
comment:8 Changed 9 years ago by txm.fourier@…
Any movement on this? Is it absolute neccesity to use tarballs (which doesn't exist) to be accepted to macports?
comment:9 Changed 9 years ago by txm.fourier@…
Ping guys. You have a package and a maintainer here, what is the problem?
comment:10 Changed 8 years ago by kurthindenburg (Kurt Hindenburg)
Cc: | kurthindenburg added |
---|
It looks like 1.6 was released 5 months ago - can you update the Portfile to use that and I'll commit it for you.
Patch to be able to compile