#58: allow darcs repo to be specified in cabal file ----------------------------+----------------------------------------------- Reporter: ijones | Owner: Type: enhancement | Status: new Priority: high | Milestone: Cabal-1.6 Component: Cabal library | Version: Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.2.1 | Platform: Linux ----------------------------+----------------------------------------------- Changes (by SamB): * cc: SamB (added) Comment: The SCM field is indeed rather vital, given that almost every distributed SCM supports fetching via HTTP in addition to SSH and any native protocol it may have. Anyway, it's simpler to implement that way. It would probably also be good to keep a registry of SCM names for the rare occasion where it isn't obvious what to put in the field -- arch comes to mind, and I guess there might be some confusion regarding mercurial/hg. Speaking of arch, some SCMs will very possibly require further parameters -- in arch's case, the branch to check out -- and others may benefit -- e.g. git could use a branch name, though {{{master}}} makes a reasonable default. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/58#comment:11 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects