[arch-haskell] Stable, Vetted Hackage

Ethan Schoonover es at ethanschoonover.com
Thu Dec 13 22:33:10 CET 2012

I'd also like to encourage the arch-haskell team to talk to Michael on
this. The current Haskell repos have made things so much better than they
were even a year ago, but if we can get behind a rising tide to lift all
boats, I'd love to see that happen. I am still end user / novice enough to
feel unqualified to evaluate Michael's proposals on a technical level other
than they seem reasonable, maintainable and scalable as far as I can see.
He's out in front on this, which is what Haskell needs right now. Let's get



On Wed, Dec 12, 2012 at 8:10 AM, Michael Snoyman <michael at snoyman.com>wrote:

> I definitely think there's a lot of room for collaboration here. I've been
> in touch with maintainers for other Linux distributions, and I think
> Stackage could become a project where different distros are all able to
> work together. Stackage is also set up in a way right now that seems to fit
> Arch's rolling release cycle.
> To start off with, I would recommend using Stackage as a way to get a list
> of packages and their versions which work together correctly (the generated
> build-plan.log). You could then use automate a process to make Arch
> versions of all those packages.
> Stackage provides a library in addition to an executable, and it can be
> extended to provide support for whatever facilities you need. This would
> also allow you to add in packages which are not currently part of the
> "official" Stackage set of packages. By using Stackage, you'll get a few
> benefits:
> * A tool which is well tested for confirming that packages work well
> together.
> * The ability to work with other developers outside of Arch to improve
> this tooling.
> * As a community resource, I think Stackage stands a better chance of
> getting necessary modifications merged upstream. I've so far had very
> positive responses from package maintainers I've interacted with; I don't
> think a requested change has yet taken over a week to get implemented.
> All that said, I'm not intimately familiar with the Arch Haskell processes
> and what hurdles you're trying to overcome. If you have concrete
> objectives, let me know what they are, and I'd be happy to figure out with
> you if Stackage would help achieve them.
> Michael
> On Wed, Dec 12, 2012 at 5:55 AM, Ramana Kumar <ramana at member.fsf.org>wrote:
>> Dear Michael, Arch Haskell,
>> I saw this in the Haskell Weekly News recently:
>> http://www.yesodweb.com/blog/2012/11/stable-vetted-hackage
>> I would like to propose that Arch Linux and the Hackage-packaging
>> community project therein also be involved :)
>> Some information about the Arch Haskell project is here
>> https://wiki.archlinux.org/index.php/Haskell_package_guidelines
>> I believe yesod and its dependencies, for example, are available in our
>> [haskell-web] repository, and we (mainly Fabian and Magnus) are doing a
>> great job of keeping it all working and up-to-date.
>> How might this interface with stackage?
>> Do you (on either side) see potential for collaboration?
>> Cheers,
>> Ramana
> _______________________________________________
> arch-haskell mailing list
> arch-haskell at haskell.org
> http://www.haskell.org/mailman/listinfo/arch-haskell
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20121213/52cc2d46/attachment.htm>

More information about the arch-haskell mailing list