[arch-haskell] darcs unbuildable

Vesa Kaihlavirta vpkaihla at gmail.com
Sat Oct 12 07:37:29 UTC 2013

> The same situation holds for haskell-http and haskell-network at the moment.

These are fixed now, and darcs-2.5 is in extra.

> It would be nice to know whether we in the archhaskell team can rely on
> the HP
> packages (such as parsec, HTTP, network, etc) that happen to be in
> [extra]/[community], will be kept on the HP versions.  If that is the case,
> then we can provide a binary repo that complements [extra]/[community].
> Is this the goal?

It definitely is the goal, and perhaps we should try to find a way to
make it less easy to accidentally upload packages that break the
platform compliance. Arch users tend to be a bit... needy when it
comes to new upstream versions, and devs that aren't familiar with the
Arch Haskell thing may think they're helping when they upgrade
according to the users' wishes.

Some ideas:

  1) we make a haskell-platform package that does not provide the
packages that are within, but other packages instead are expected to
depend on the platform instead of the separate packages.

  2) we define haskell-platform as arch linux metapackage (I'm not
sure if this will help with forcing the versions at all)

  3) we have an empty haskell-platform package that depends on the
specific versions of the haskell-platform packages

As a packager, I kinda like 1) because it feels the most Archy insofar
that it would result in the smallest amount of packages.


More information about the arch-haskell mailing list