[arch-haskell] pandoc in the repositories

Don Stewart dons at galois.com
Tue Feb 24 12:46:06 EST 2009


abhidg:
> 2009/2/15 Don Stewart <dons at galois.com>:
> > abhidg:
> >> 2009/2/15 Don Stewart <dons at galois.com>:
> >> > Knowing John, you could probably just ask the developer to make this
> >> > split upstream.
> >> >
> >>
> >> OK, I've opened an issue in the upstream bugtracker:
> >> http://code.google.com/p/pandoc/issues/detail?id=126
> >
> > Excellent!
> >
> 
> The split can be easily done using cabal or using runhaskell,
> from John's comment on issue 126 in pandoc's bugtracker.
> 
> I've prepared two packages: haskell-pandoc and pandoc.
> haskell-pandoc depends on the ghc toolchain and the other
> haskell libraries; it also depends on pandoc.
> pandoc contains only the binary 'pandoc', some helper scripts
> and the manual pages. Thus the pandoc package only needs to
> depend on gmp and zlib.
> 
> Doing `pactree -u haskell-pandoc` (pactree is in pacman-contrib)
> gives the dependency chain of haskell-pandoc as:
> 
> ghc
> gmp
> gcc-libs
> glibc
> kernel-headers
> tzdata
> texinfo
> ncurses
> findutils
> gzip
> bash
> readline
> libedit
> haskell-utf8-string
> haskell-zip-archive *
> haskell-binary *
> haskell-digest *
> zlib
> haskell-zlib
> pandoc
> 
> Of these the * ones are not yet in [community], but they need to be if
> pandoc is to be updated to 1.1.


And my general view is that if a Haskell app needs some Haskell libs, we
should move them in.


More information about the arch-haskell mailing list