Hi everyone. I noticed that as soon as a new patchlevel release of
ImageMagick becomes available, the old patchlevel archives disappear
and become symlinks to the new version:
ftp://ftp.imagemagick.org/pub/ImageMagick/
I object to this because it's inaccurate. If I request to download
6.3.4-3, then that's what I want to receive. I don't want to receive
6.3.4-4 unless that's what I requested.
I'm the maintainer of the MacPorts portfile for ImageMagick. MacPorts
works by defining a download location and checksums for a given
version of a given piece of software. This ensures that the version
the user downloads and installs is the same one the portfile author
tested and qualified. MacPorts even lets you define multiple download
locations for a software package, so that if a server goes offline or
a particular version of the software is removed from one of the
servers, it can get it from another server. But your symlinking
strategy breaks this. When MacPorts tries to download, say, 6.3.4-3
from your server, it's not that the server is unavailable, and as far
as MacPorts can tell, it's not that the archive is unavailable (since
you're not sending a 404 HTTP status code). Rather, as far as
MacPorts can tell, it has requested the archive for 6.3.4-3, and
received the archive for 6.3.4-3, but its checksum doesn't match the
one recorded in the portfile, so it balks and prints an error.
Would it be possible for you to keep the old tarballs around, at
least for a week or two after a new release? This would give those of
us at MacPorts and those with Fink and FreeBSD ports and Gentoo
Portage and all the other package managers time to update our package
definitions.
Thank you for your consideration.
_______________________________________________
Magick-users mailing list
[email protected]
http://studio.imagemagick.org/mailman/listinfo/magick-users
