[Haskell-cafe] Listing native package requirements based on cabal information
davidleothomas at gmail.com
Wed Mar 19 14:42:18 UTC 2014
Yeah, it seems that there are a number of potentially good options that are
going to vary by distro and situation, which is why I've been thinking
"hook to run arbitrary script". Sufficiently populating the lookup table
for that script for any given (Project, Distro) shouldn't be hard, and
collecting those we should be able to quickly 1) round the rough edges off
of the more common cases without requiring too much manual intervention,
and 2) have a reasonable path for the less common cases.
On Wed, Mar 19, 2014 at 5:48 AM, Alexander V Vershilov <
alexander.vershilov at gmail.com> wrote:
> In Gentoo Linux we use a common ebuild format that allowes to add native
> dependencies to packages.
> To create a ebuild from cabal file we use tool called hackport .
> This approach allow to bump dependencies when some authors are to lazy to
> bump them themselves,
> even in presence of pull requests, and add compatibility patches. Also
> it's possible to create a desktop-icons,
> additional files, filter test/bench programs that should not be installed
> into system. Also it supports a dependency
> on package flags and profiling.
> However this approach doesn't scale on other distros in a easy way, one
> possibility is to create static
> packages using emerge, but this area require some more research.
>  http://hackage.haskell.org/package/hackport
> On 18 March 2014 20:26, David Thomas <davidleothomas at gmail.com> wrote:
>> Is there a way to extract this? I'm looking to make it easier for
>> newcomers to my project to get things building across different linux
>> Haskell-Cafe mailing list
>> Haskell-Cafe at haskell.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Haskell-Cafe