[Haskell-cafe] Experiences with cabal-install and Hackage

[Christopher Done]

I don't know how wise that is; I tend to fix packages when I find
they're broken. I'd prefer a way for there to be more than one
maintainer for a package, i.e., collaborators, like on Github, so that
a maintainer can add me as a collaborator. My only problem with
Hackage is I feel like the maintainer is a fence I have to climb every
time I want to upload a bugfix or a non-broken version of the package.
I just want to fix it, upload it, and continue with my work. Also a
"last seen" a la StackOverflow would be good, so that you can see what
a maintainer was last on Hackage. That's assuming the new Hackage will
support logins.

On 22 July 2010 09:52, Isak Hansen <isak.hansen at gmail.com> wrote:
> On Thu, Jul 22, 2010 at 9:16 AM, Ketil Malde <ketil at malde.org> wrote:
>>
>> I've rather recently started to use cabal-install to install packages
>> from Hackage.  Unfortunately, so far many packages fail to install.  I
>> try to email authors/maintainers, but when I check build logs on
>> Hackage, I discover that some of these packages have failed building for
>> some time.
>>
>> Wouldn't it make sense to provide automated notification of the package
>> author when a package fails to build?  I certainly would like to know
>> about it, but of course, I never remember to check back to see.
>>
>
> How about taking it one step further, actually "hiding" unmaintained
> packages after a grace period?
>
> Unless the user runs cabal with an --include-deprecated option, or something.
>
>
> Isak
>
>> -k
>> --
>> If I haven't seen further, it is by standing in the footprints of giants
>> _______________________________________________
>> Haskell-Cafe mailing list
>> Haskell-Cafe at haskell.org
>> http://www.haskell.org/mailman/listinfo/haskell-cafe
>>
> _______________________________________________
> Haskell-Cafe mailing list
> Haskell-Cafe at haskell.org
> http://www.haskell.org/mailman/listinfo/haskell-cafe
>