can I indicate that an old version is not to be used, and some more questions

[S. Doaitse Swierstra]

I of course test things on my machine before uploading; it is only that I do not have several Haskell compilers installed, nor all versions of package base, etc. Having this at a single location would make life easier and cabal files more reliable. I can test the code on my machine, but not the installation process in other environments.

 Doaitse


On 23 jul 2010, at 11:13, Henning Thielemann wrote:

> 
> On Fri, 23 Jul 2010, Sittampalam, Ganesh wrote:
> 
>> There's work going on in this area with the hackage 2 server, but I
>> think it'll mostly come in the form of getting build reports after a
>> package has been published, rather than having them rejected before
>> publication. The more work the hackage server itself is expected to do,
>> the harder it will be to maintain, so the proposed architecture is for
>> other people to be able to submit build reports.
> 
> For me the best solution would neither be letting Hackage reject packages automatically, nor waiting for build report of others, but being able to run a dependency checker on my machine before uploading. Even today I use a script that tries to compile the package from the tarball before uploading. This way I can quickly spot files, that I forgot to include in the Cabal file. No need to wait for Hackage or other users. It would be nice to have this for version consistency, too.
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://www.haskell.org/mailman/listinfo/libraries