[Hackage] #58: darcs integration idea: track location of darcs repo, create new repo

[Hackage]

#58: darcs integration idea: track location of darcs repo, create new repo
--------------------------------+-------------------------------------------
  Reporter:  ijones             |        Owner:  ijones   
      Type:  enhancement        |       Status:  new      
  Priority:  high               |    Milestone:  Cabal-1.4
 Component:  HackageDB website  |      Version:           
  Severity:  normal             |   Resolution:           
  Keywords:                     |   Difficulty:  normal   
Ghcversion:  6.2.1              |     Platform:  Linux    
--------------------------------+-------------------------------------------
Comment (by duncan):

 We need a spec for how we should specify the source control in a .cabal
 file.

 Here are some questions to consider. They are not necessarily all
 requirements.

  * what are the use cases?
  * what kinds of integration would we like with other tools, eg hackage or
 cabal-install.
  * how to specify the kind of source control being uses, eg darcs, svn,
 git etc. Though it's for hackage to support darcs better than others we
 should allow all necessary info for other systems to be specified in the
 .cabal file for other tools to take advantage of.
  * how to specify the url, does that work for other SCMs?
  * what about tags or branches?
  * what if the package is not at the root of the repo but within some sub-
 dir? We may want to find it.
  * should we be specifying the repo/tag for the exact release? should we
 specify the branch this release was made from or the main development
 branch, or both?

-- 
Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/58#comment:3>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects