#58: allow dev 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 ----------------------------+----------------------------------------------- Comment (by duncan): A similar proposal for the RPM packaging system: http://lwn.net/Articles/290300/ {{{ SCMType: {cvs|svn|git|hg|etc.} SCMRepo: <repo_url, complete spec for SCMs like git, would be cvs_root for cvs> SCMModule: <module name for repo types that need this, such as cvs> SCMTag: <tag representing exact source matching binary package> SCMBranch: <branch on which tag exists, allowing the installation of later sources from the same product line branch instead of exact sources of the installed package at the user's option> }}} Clearly we need to know which scm we're dealing with. But I think we also want to be able to refer to more specific things, in particular the 'HEAD' branch where new development happens and also the branch from which this release was made (if different) and optionally a tag for this specific release. Not all that information is required of course, but we should be able to specify it in a clear way. If the meaning is well defined then it allows us to to integration like rebuilding from the same branch+tag, following activity in a head repo (for info on the hackage website). If we don't give clear meanings it's almost useless, it can then only be used as a link for humans to follow and interpret. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/58#comment:13> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects