On 26/08/13 10:32, Jens Axel Søgaard wrote:
> One easy improvement, when using github, is to allow/ensure package
owners point to a
> specific release/tag .zip file and not worry about the checksum as
nothing is going to
> change until a new release/tag is specified.
It is not as easy as it seems. Let's say I write module A which uses
specific versions of packages B and C.
Packages B and C both use package D. Here is the twist: package B is
written to use the latest version of
package D and C uses version 42.
Now package D is updated. The checksums of B and C do not change, but
the behavior of B might.
I understand the scenario that you are explaining and it illustrates a
further problem: If two packages rely on the api
of different checksumed packages, one is going to lose out under the new
package manager as they will both
have to use the same release of a package, which may have a different
and incompatible api to that expected.
My proposal to point to a specific release is actually a moot point as I
noticed from Jay McCarthy's reply that this
can be done and indeed I had forgotten that this was mentioned in the
docs. I have now updated the source
for my package xdgbasedir to point to the latest tag that I wanted to
release.
Lorry
--
vLife Systems Ltd
Registered Office: The Meridian, 4 Copthall House, Station Square, Coventry,
CV1 2FL
Registered in England and Wales No. 06477649
http://vlifesystems.com
____________________
Racket Users list:
http://lists.racket-lang.org/users
