Hi Bardur,
https://github.com/haskell/cabal/issues/2004 is another bug that seems like
it could be related. The idea is to use a single sandbox across multiple
packages so if you have a directory layout like
top/
application/
library1/
library2/
If you were to then:
cd top, cabal sandbox
On 06/19/2015 08:59 PM, Thomas Tuegel wrote:
[--snip--]
Thank you, I'll have a thorough look at everything you pointed out
tomorrow. Likewise for anyone else who'd care to chime in! :)
Regards,
___
cabal-devel mailing list
cabal-devel@haskell.org
http:
On Fri, Jun 19, 2015 at 1:14 PM, Bardur Arantsson wrote:
> Hi all,
>
> Given that I'm often quite annoyed by the almost-total lack of support
> for developing a set of coherent libraries together in a convenient
> fashion[1] using Cabal, I'd like to ask
>
> a) are there any current plans or GitHub
On 06/19/2015 08:14 PM, Bardur Arantsson wrote:
> Hi all,
>
[--snip--]
Oh, yes, I should add. I've been thinking about a couple of approaches
for how to achieve this ("UI-wise" so to speak) and would like some
"guesstimate" of feasibility by people in the know.
1st approach: Use a single cabal f
Hi all,
Given that I'm often quite annoyed by the almost-total lack of support
for developing a set of coherent libraries together in a convenient
fashion[1] using Cabal, I'd like to ask
a) are there any current plans or GitHub issues on implementing any
support for this workflow that I should be