new Darcs-Repository field?
Björn Bringert suggested that the Hackage page for a package should include a link to the Darcs repo (if any, but who uses anything else?) and maybe some darcs integration such as changelogs and the like. To make this work, we'd need a URL-valued Darcs-Repository field in the package description.
Ross Paterson
Björn Bringert suggested that the Hackage page for a package should include a link to the Darcs repo (if any, but who uses anything else?) and maybe some darcs integration such as changelogs and the like. To make this work, we'd need a URL-valued Darcs-Repository field in the package description.
I'm all for it. I'd love tighter integration with darcs. FYI, I think that's what some people use the package-url for. We could also do a "pull" for such packages and host a version of the repo on hackage. If there's no darcs-repository, we could just create one so we'd have a local version. It would be great if Hackage could some day become the "public" repo for many darcs projects, without having to give folks login accounts. I picture a place where people can send patches (packagename@hackage.haskell.org), and the owner(s) of the repo would have a UI for browsing and accepting / applying patches. Signed packages by approved folks would get applied automatically. Cabal-install could have a --get-repo option, so when the user fetches the source, they get a darcs repository. In Debian, the maintainers are distinct from the upstream developers, and the same might be true in Hackage. Debian uses tarred patches to maintain the differences between the trees, but we could use darcs. If a package sits unmaintained for a while... maybe the upstream author has stopped applying patches, then people could volunteer to take over the package or fork it. To some extent these are juts darcs user interface ideas, but I think that the combination of a version control system and a package manager has a lot of possibilities. So many possibilities :) peace, isaac
On Thu, 2007-01-04 at 15:15 +0000, Ross Paterson wrote:
Björn Bringert suggested that the Hackage page for a package should include a link to the Darcs repo (if any, but who uses anything else?) and maybe some darcs integration such as changelogs and the like. To make this work, we'd need a URL-valued Darcs-Repository field in the package description.
I think this is a good idea. Can we get away with only allowing darcs? :-) Here's what gentoo has for its global overlay configuration file (a gentoo overlay is a tree of ebuild files usually managed in a version control system): <overlay type = "svn" src = "https://gentooscience.org/svn/overlay" contact = "sci@gentoo.org" status = "official" name = "science"> <overlay type = "rsync" src = "rsync://rsync.breakmygentoo.net/bmg-main/bmg-main" contact = "bugs.breakmygentoo.net" name = "break-my-gentoo-main"> <overlay type = "darcs" src = "http://www.haskell.org/~gentoo/gentoo-haskell/" contact = "haskell@gentoo.org" status = "official" name = "haskell"> <overlay type = "tar" src = "http://geki.ath.cx/OOo/openoffice.tar.bz2" contact = "h.mth@web.de" name = "openoffice-geki"> etc, you get the idea. So they have a 'type' field as well as a url for it. We could do the same and for the moment only implement stuff for darcs. How about: rcs-type: rcs-url: Hmm ok, not so good. Someone come up with something less cryptic :-) Duncan
Hi
Can we get away with only allowing darcs? :-)
If we only allow darcs, that will persuade more Haskell developers to migrate to darcs, and will simplify the life for Haskell users. If there was a free hosting place which offered darcs repo's then the answer is probably yes. Yhc depends on one svn repo, and its annoying to introduce an additional dependancy. Thanks Neil
Ross Paterson wrote:
Björn Bringert suggested that the Hackage page for a package should include a link to the Darcs repo (if any, but who uses anything else?) and maybe some darcs integration such as changelogs and the like. To make this work, we'd need a URL-valued Darcs-Repository field in the package description.
Trac uses a syntax like 'VC:FILE' for the repo, eg. 'darcs:/home/darcs/ghc'. Perhaps we could do the same, something like source-repository: darcs:http://darcs.haskell.org/happy or is that too many colons? :) The syntax of the thing after the 'darcs:' is entirely VC-dependent, of course. Cheers, Simon
On Jan 15, 2007, at 16:54 , Simon Marlow wrote:
Ross Paterson wrote:
Björn Bringert suggested that the Hackage page for a package should include a link to the Darcs repo (if any, but who uses anything else?) and maybe some darcs integration such as changelogs and the like. To make this work, we'd need a URL-valued Darcs-Repository field in the package description.
Trac uses a syntax like 'VC:FILE' for the repo, eg. 'darcs:/home/ darcs/ghc'. Perhaps we could do the same, something like
source-repository: darcs:http://darcs.haskell.org/happy
or is that too many colons? :) The syntax of the thing after the 'darcs:' is entirely VC-dependent, of course.
I think that we may also need to be able to specify a directory inside a darcs repo, since many darcs repos contain multiple Cabal packages. For example, the Cabal repo contains Cabal, cabal-setup and cabal-install. I guess programs could just search in the repo for a .cabal file for the right package, but that means having to do a darcs get. Whether that's ok or not depends on what the field is used for I suppose. /Björn
participants (6)
-
Bjorn Bringert -
Duncan Coutts -
Isaac Jones -
Neil Mitchell -
Ross Paterson -
Simon Marlow