Hi,
On Wed, Sep 5, 2012 at 12:38 AM, Johan Tibell wrote:
> On Tue, Sep 4, 2012 at 2:17 PM, Mikhail Glushenkov
> wrote:
>> I looked more closely into this, and it seems like the easiest
>> solution is a --no-download flag for "install". It can be implemented
>> either by exiting with error if the
On Tue, Sep 4, 2012 at 2:17 PM, Mikhail Glushenkov
wrote:
> I looked more closely into this, and it seems like the easiest
> solution is a --no-download flag for "install". It can be implemented
> either by exiting with error if the install plan contains packages
> that aren't already installed (f
Hi,
On Tue, Sep 4, 2012 at 12:52 AM, Johan Tibell wrote:
> On Mon, Sep 3, 2012 at 12:50 PM, Mikhail Glushenkov
> wrote:
>> -It's just that I had a version using install already working. It'll
>> take me a bit more time to make it use configure/build/register
>> instead. I'm a bit busy right now,
Well, I'm not sure. Perhaps some form of name allocation is appropriate,
as it could theoretically lead to problems when you want to use package A
alongside package B, which both rely on two different packages with
conflicting module names. On the other hand, this case doesn't
necessarily ca
On Tue, Sep 04, 2012 at 06:49:00PM +0100, Ross Paterson wrote:
> On Tue, Sep 04, 2012 at 06:32:48PM +0100, Leon Smith wrote:
> > Ok, when I upload a package it warns me about unallocated names? How are
> > names allocated, and who makes the decisions here?
>
> It's complaining if the first com
On Tue, Sep 04, 2012 at 06:32:48PM +0100, Leon Smith wrote:
> Ok, when I upload a package it warns me about unallocated names? How are
> names allocated, and who makes the decisions here?
It's complaining if the first component of a hierarchical module name
doesn't come from a certain set. Th
Ok, when I upload a package it warns me about unallocated names? How are
names allocated, and who makes the decisions here?
Best,
Leon
___
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org/mailman/listinfo/cabal-devel
On Mon, Sep 03, 2012 at 04:32:16PM +0100, Ross Paterson wrote:
> On Mon, Sep 03, 2012 at 03:52:32PM +0100, Erik Hesselink wrote:
> > On Mon, Sep 3, 2012 at 4:38 PM, Ross Paterson wrote:
> > > In Hackage 1 packages can be deprecated, optionally indicating a
> > > recommended replacement (the "depre
On Mon, Sep 03, 2012 at 03:38:19PM +0100, Ross Paterson wrote:
> A few minor issues:
Thanks for the feedback!
> Several packages lack documentation. They don't say why (an issue in
> itself),
I've made a ticket for this:
https://github.com/haskell/cabal/issues/1024
> but it appears to be libra
