[arch-haskell] Creating binary and doc from the same PKGBUILD

Magnus Therning magnus at therning.org
Sat Oct 12 07:35:22 UTC 2013

Abhishek Dasgupta wrote:
> 2009/8/7 Magnus Therning <magnus at therning.org>:
>> I assume that statement indicates that putting haskell-dataenc documentation
>> in /usr/share/doc/ghc/libraries/dataenc isn't policy compliant?
> [snip]
> According to
> http://wiki.archlinux.org/index.php/Arch_Packaging_Standards:
> /usr/share/doc/{pkg} Application documentation
> So haskell-dataenc documentation should go into
> /usr/share/doc/haskell-datenc; some packages install version names as well
> in the folder name, but that would cause the folder name to change on every
> upgrade.

The PKGBUILD and .install generated by cabal2arch already results in packages
that prevent multiple versions of the same library to be installed at the same
time, so I'll put the documentation in /usr/share/doc/${pkgname}.

> While it is fine to ship the documentation with the package itself, quite a
> bit of space would be wasted if/when someone sets up a binary repository of
> the haskell packages. I do not know how much the standard space requirements
> for haddock-generated documentation is, though. In Arch, the convention is
> to include small documentation in the package itself and for larger
> documentation split it out into a -doc package (example: python-docs).

What size is "big"?  I suspect that the only haskell package containing enough
docs to warrant a separate -doc package is GHC itself.


Magnus Therning                        (OpenPGP: 0xAB4DFBA4)
magnus@therning.org          Jabber: magnus@therning.org
http://therning.org/magnus         identi.ca|twitter: magthe

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: OpenPGP digital signature
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20131012/fdc9486c/attachment.sig>

More information about the arch-haskell mailing list