Created attachment 207276 [details]
Changelog is here:
This patches includes:
- proper modification to the meta port `lang/julia`
- minor changes in lang/julia06 and lang/julia07
- passed on FreeBSD 12.0-RELEASE amd64 with default OPTIONS
- passed on FreeBSD 12.0-RELEASE amd64 with OPENLIBM enabled
- passed on FreeBSD 12.0-RELEASE amd64 with OPENBLAS enabled
- passed on FreeBSD 12.0-RELEASE amd64 with all OPTIONS enabled
- passed on FreeBSD 12.0-RELEASE i386 with default OPTIONS
- passed on FreeBSD 12.0-RELEASE i386 with OPENLIBM enabled
- passed on FreeBSD 12.0-RELEASE i386 with OPENBLAS enabled
- passed on FreeBSD 12.0-RELEASE i386 with all OPTIONS enabled
Are you sure that we need to add one more version of Julia?
Should separate patches for the new port and the lang/julia 1.0.4 update into separate issues and have this one depend on the latter if the new port is based off the existing port update
(In reply to Li-Wen Hsu from comment #1)
yeah, since Julia v1.1 doesn't reach the end of life, I want to add a new port for v1.2.
(In reply to Kubilay Kocak from comment #2)
hmm, there are some options listed in lang/julia requires the existence of lang/julia12 (this new port).
I think it's not easy to read/check if I split this patch into two parts.
Maintainer is checking issues on 11.3.
Any update on this one? If is has no issues on 12, we can mark 11 as IGNORE first.
The issue is same as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235891.
If user has a newer ld, the error will be popped up.
lang/julia10 (the current LTS according to https://julialang.org/downloads/ ) hinges on Python 2.7 so will be removed tomorrow, it might be worthwhile to update this port to 1.5.3 (the latest non-LTS) or create a lang/julia15 instead of lang/julia10? That is, if it uses Python 3.6+
(In reply to Rene Ladan from comment #8)
It seems that julia does not depend on Python anymore.
Note: I would prefer to have only one un-versioned of julia, as we had previously, before the meta-port. I.e. repocopy lang/julia11 to lang/julia.