Migration issue
Ryan Schmidt
ryandesign at macports.org
Mon Dec 21 14:49:30 PST 2015
On Dec 16, 2015, at 4:33 PM, Mojca Miklavec wrote:
> Oh, this reminded me on the following thread from the past:
> https://lists.macosforge.org/pipermail/macports-dev/2013-July/023498.html
>
> Ryan, does the following patch help?
>
> --- Portfile (revision 143624)
> +++ Portfile (working copy)
> @@ -37,8 +37,9 @@
> 5.22 1 0 99e3af98d80ace857da6ce28679a2e35a4360144
> e98e4075a3167fa40524abe447c30bcca10c60e02a54ee1361eff278947a1221
> }
>
> -foreach {perl5.major perl5.subversion perl5.revision perl5.rmd160
> perl5.sha256} ${perl5.versions_info} {
> - subport perl${perl5.major} {
> +foreach {perl5.v perl5.subversion perl5.revision perl5.rmd160
> perl5.sha256} ${perl5.versions_info} {
> + subport perl${perl5.v} {
> + set perl5.major ${perl5.v}
> version ${perl5.major}.${perl5.subversion}
> set minor [lrange [split ${version} .] 1 1]
> revision ${perl5.revision}
I think I forgot to respond, but yes, that was the type of solution I was going to suggest, and it seems to have resolved the problem.
More information about the macports-dev
mailing list