[Hackage] #258: case confusion - cabal vs Cabal
#258: case confusion - cabal vs Cabal ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ----------------------------+----------------------------------------------- The darcs repo for Cabal is at darcs.haskell.org:/home/darcs/cabal yet it contains a file Cabal.cabal, which indeed claims that the name of the package is Cabal. This confusion of letter case is causing problems for me. Can we agree that Cabal is capitalised, and rename the repo dir? That seems like the simplest way to achieve consistency. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/258 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#258: case confusion - cabal vs Cabal ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Resolution: wontfix Keywords: | Difficulty: normal Ghcversion: 6.8.2 | Platform: ----------------------------+----------------------------------------------- Changes (by kolmodin): * status: new => closed * resolution: => wontfix Comment: The name of the package is indeed Cabal, with a capital C. Renaming either the name of the .cabal file or the repo dir is not trivial though. * Changing the name of the .cabal file would also require to rename the package, since hackage requires the file name to be consistent with the package name. This would effectively break all packages depending on Cabal, and of course make much hassle with forward and backwards compatibility. * Renaming the repo name would break the darcs installations of all our developers, something we are really not keen to do. We could set up a symlink to use the {{{Cabal}}} name, but I'd find that even more confusing than just having a single repository. http://www.orlyowl.com/upload/files/NOOOO!!!.JPG -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/258#comment:1 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#258: case confusion - cabal vs Cabal ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Resolution: wontfix Keywords: | Difficulty: normal Ghcversion: 6.8.2 | Platform: ----------------------------+----------------------------------------------- Comment (by maltem): This does raise another question: Should upper case be allowed in package names at all? It makes handling of packages a rather tedious task (was it openGL or Opengl or ...) It's also interesting to note that most package maintainers tend towards all-lowercase, including the packages that came out of the base split. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/258#comment:2 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#258: case confusion - cabal vs Cabal ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Resolution: wontfix Keywords: | Difficulty: normal Ghcversion: 6.8.2 | Platform: ----------------------------+----------------------------------------------- Comment (by duncan): Note that `cabal-install` is mostly case insensitive in its user interface. For example: {{{ cabal list opengl cabal install opengl }}} Will work just fine. That's because "opengl" is not ambiguous. If there were an "Opengl" and an "OpenGl" package then `cabal list opengl` would list both, but `cabal install opengl` would complain and you'd have to use `cabal install OpenGL` exactly. It's ok for distro packages to use all lower case even if the haskell package uses mixed case. The promise is that there will be no overlaps (with the one exception that packages can rename themselves to a different case, but in that case it's still really the same package.) -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/258#comment:3 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
#258: case confusion - cabal vs Cabal ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Resolution: wontfix Keywords: | Difficulty: normal Ghcversion: 6.8.2 | Platform: ----------------------------+----------------------------------------------- Comment (by guest): Hoogle uses lowercase for packages and initial-upper-case for modules. i.e. +tagsoup will search the tagsoup package, +TagSoup will search the tagsoup module. I think cabal packages should be strongly suggested to be all lower-case. This has lead to a great source of confusion, with everyone picking entirely different naming conventions: http://neilmitchell.blogspot.com/2008/05/interactive-tagsoup-parsing.html i.e. about 1/6 of packages have an initial capital. I'd mandate cabal packages to be case insensitive (they probably are on windows anyway!) and start displaying them all lower case. The cabal convention for fields is hyphen-separators, so that should be the standard way of distinguishing packages. -- Neil -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/258#comment:4 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects
participants (1)
-
Hackage