Unallocated names

[Leon Smith]

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 cause problems either.

It doesn't seem useful at the moment,  in it's current incarnation.   So
I'd say we probably ought to turn it off.

Best,
Leon

On Tue, Sep 4, 2012 at 2:22 PM, Ian Lynagh <ian at well-typed.com> wrote:

> 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 component of a hierarchical module name
> > doesn't come from a certain set.  There was once a plan to allocate
> > the module namespace, but it's pretty dormant:
> >
> > http://www.haskell.org/haskellwiki/Hierarchical_module_names
>
> Leon's presumably talking about postgresql-simple-0.2.4.1, which uses
> Database.PostgreSQL.*
>
> Hackage2 will currently complain about anything that doesn't start with
> one of:
>     Algebra, Codec, Control, Data, Database, Debug, Distribution,
>     DotNet, Foreign, Graphics, Language, Network, Numeric, Prelude,
>     Sound, System, Test, Text
>
> Does anyone think that this check is currently useful, or should I just
> turn it off?
>
>
> Thanks
> Ian
>
>
> _______________________________________________
> cabal-devel mailing list
> cabal-devel at haskell.org
> http://www.haskell.org/mailman/listinfo/cabal-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/cabal-devel/attachments/20120904/837b1609/attachment.htm>