[124941] trunk/dports/devel/libical/Portfile

Ryan Schmidt ryandesign at macports.org
Sun Aug 31 16:58:05 PDT 2014


> On Aug 31, 2014, at 6:37 PM, khindenburg at macports.org wrote:
> 
> Revision
> 124941
> Author
> khindenburg at macports.org
> Date
> 2014-08-31 16:37:26 -0700 (Sun, 31 Aug 2014)
> Log Message
> 
> libical: move to github
> Modified Paths
> 
> 	• trunk/dports/devel/libical/Portfile
> Diff
> 
> Modified: trunk/dports/devel/libical/Portfile (124940 => 124941)
> 
> --- trunk/dports/devel/libical/Portfile	2014-08-31 21:39:47 UTC (rev 124940)
> +++ trunk/dports/devel/libical/Portfile	2014-08-31 23:37:26 UTC (rev 124941)
> 
> @@ -2,17 +2,15 @@
> 
>  # $Id$
> 
>  
> 
>  PortSystem          1.0
> 
> +PortGroup           github 1.0
> 
>  
> 
> -name                libical
> -version             1.0
> 
> +github.setup        libical libical 1.0 v
> 
>  categories          devel
> 
>  license             {LGPL-2.1 MPL-1}
> 
>  maintainers         nomaintainer
> 
>  description         An implementation of iCalendar protocols and data formats
> 
>  long_description    ${description}
> 
>  platforms           darwin
> 
> -homepage            http://sourceforge.net/projects/freeassociation/
> 
> -master_sites        sourceforge:freeassociation
> 
>  
> 
>  checksums           rmd160  1c78b07c37c80e8fe068fb3164bbf8614f02e67f \
> 
>                      sha256  7c39b3448e4927a2de2775d853f52b3aaeb42400970a3db0b01a78987e6ec0b7

This will not fetch from github; it will get 404 not found because the tag name on github is 1.0.0 not 1.0. This is not actually a problem, since the old sourceforge distfile is already mirrored by the MacPorts distfiles mirrors.

If you change the version to 1.0.0, then the checksums will not match, because the file on sourceforge was manually packaged, while the file on github is automatically generated from the repository. The two tarballs extract to directories of different names. Their contents are identical however.

You may want to switch back to the sourceforge master_sites until the next update.




More information about the macports-dev mailing list