Need a username for Hackage
Hi Ross. (CC cabal-devel) I'm adding all packages from hackage to the nix distribution system. However I'v noticed some small issues. (eg Renaming FilePath -> filepath) Should I fix the issues in nix only or should I fix the packages on hackage? If so I would need an account on hackage. Marc Weber
marco-oweber:
Hi Ross. (CC cabal-devel)
I'm adding all packages from hackage to the nix distribution system.
However I'v noticed some small issues. (eg Renaming FilePath -> filepath)
Should I fix the issues in nix only or should I fix the packages on hackage?
If so I would need an account on hackage.
Hmm, renaming the packages on hackage? Do you mean they're not found with consistent names? I don't think we want to physically rename packages -- that'll break other distros. -- Don
Hi Neil, (John Goerzen) The affected packages having FilePath instead of filepath in their dependency lists are: dfsbuild HSH hpodder They are all maintained by John Goerzen, that's why I've cc'd this message. I'm not quite sure. But I think I had registered one of the early versions with that name as well (Long before it has been uploaded to hackage).. But it might be the case that just I had given it this name. I've tried installing hpodder some days ago. That's why I was faced this problem more frequently ;) Marc Weber
Hi
The affected packages having FilePath instead of filepath in their dependency lists are:
dfsbuild HSH hpodder
Yes, unfortunately I originally picked the name FilePath, but all the standard GHC packages follow the filepath convention, hence it got modified. I strongly suggest that upper case letters be banned from Cabal packages, or this is going to happen again and again. Thanks Neil
On Sun, Jul 08, 2007 at 03:29:49PM +0100, Neil Mitchell wrote:
The affected packages having FilePath instead of filepath in their dependency lists are:
dfsbuild HSH hpodder
Yes, unfortunately I originally picked the name FilePath, but all the standard GHC packages follow the filepath convention, hence it got modified. I strongly suggest that upper case letters be banned from Cabal packages, or this is going to happen again and again.
As I understand it the problem was actually that you had filepath.cabal (lowercase) containing "name: FilePath" (mixed case) (it might have been the other way round), which upsets hackage as they don't match. FWIW, Cabal and Win32 are examples of non-lower-case core libraries. Thanks Ian
Yes, unfortunately I originally picked the name FilePath, but all the standard GHC packages follow the filepath convention, hence it got modified. I strongly suggest that upper case letters be banned from Cabal packages, or this is going to happen again and again.
Could / should we add a warning when uploading packages to hackage? or when building with cabal? Then this problem would be banned ;) I think it won't harm anyone but prevent some issues. Thus it's a good thing. Marc Weber
On Sun, Jul 08, 2007 at 04:53:44PM +0200, Marc Weber wrote:
Yes, unfortunately I originally picked the name FilePath, but all the standard GHC packages follow the filepath convention, hence it got modified. I strongly suggest that upper case letters be banned from Cabal packages, or this is going to happen again and again.
Could / should we add a warning when uploading packages to hackage?
Hackage already rejects such packages, I believe.
or when building with cabal?
That would be great. Thanks Ian
participants (4)
-
dons＠cse.unsw.edu.au -
Ian Lynagh -
Marc Weber -
Neil Mitchell