[arch-haskell] How to determine whether a package is in or out in [haskell]?

Magnus Therning magnus at therning.org
Sat Oct 12 07:39:38 UTC 2013

Now we have 300+ packages in [haskell].  It's starting to be a large
set, and the time required to build when something changes is starting
to really be felt now. So I would like to start a discussion on how we
should decide what criteria to use when adding a package, and equally
important, what criteria to use when dropping a package.

My _impression_ is that additions have been a bit willy-nilly.  Guided
only by what the maintainers fancy at the moment.  I also don't think
that we've ever dropped a package, ever.

I feel it's important to me to know that the resources I put into
ArchHaskell is appreciated, and every added package increases the
resources required. I therefore would like to know that each and ever
package in [haskell] is there for a good reason.

I feel I need to bring this up because there are a few packages in
[haskell] that I suspect are there, but aren't widely used. To point
fingers, the chief reason is Agda :)  This is a package that has a
mere 13 votes in AUR, and it takes more than an hour to build it on my
laptop (about 70 minutes to be more precise). On each platform!

So, what are our options when it comes to deciding what's in and
what's out?  Any thoughts?

Oh, and can I please drop Agda in the meantime? ;)


Magnus Therning                      OpenPGP: 0xAB4DFBA4 
email: magnus at therning.org   jabber: magnus at therning.org
twitter: magthe               http://therning.org/magnus

I invented the term Object-Oriented, and I can tell you I did not have
C++ in mind.
     -- Alan Kay
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20131012/53285372/attachment.sig>

More information about the arch-haskell mailing list