What's the story re. darcs.haskell.org?

Hello folks, These may be dumb questions, but I'm afraid I haven't been keeping up with what's happening in the Haskell world recently.. So.. Is darcs.haskell.org the recommended place to start a new project? If so, who owns/runs this machine and how do I get access to it? What's the rationale for it's current organisation e.g. why is there a separate "packages" directory? (There seem to be packages elsewhere) and what's the "packages.hide" directory for? Thanks -- Adrian Hey

Hello Adrian, Tuesday, October 10, 2006, 10:02:06 PM, you wrote:
Is darcs.haskell.org the recommended place to start a new project?
i also join to these questions. if someone could produce a faq about how to make darcs repository on darcs.haskell.org for one's project, and how to manage it - it will be great -- Best regards, Bulat mailto:Bulat.Ziganshin@gmail.com

Bulat Ziganshin wrote:
Is darcs.haskell.org the recommended place to start a new project?
i also join to these questions. if someone could produce a faq about how to make darcs repository on darcs.haskell.org for one's project, and how to manage it - it will be great
Well what I have managed to find out so far is (I think:-) that this basically the old ghc cvs repository, which also holds some apparently none ghc related projects. Simon M owns/runs the machine and gives out passwords (but I guess you've gotta ask nicely :-) It's not intended to be a general communal darcs supporting sourceforge type place. But I guess most people already know this. So if darcs.haskell.org is not the right place, does anyone have any alternative suggestions? What I was looking for was the appropriate place where that users and be patch contributors could treat as a "one stop shop" for all darcsified projects (and cabalised releases). I.E. same stable URL's, easily browsable and all accessible the same way. I don't want to run my own server which provides services people expect in order to use darcs the "normal" way (whatever that might be, I'm afraid I haven't actually used darcs yet, I just want to convert a few libs I'm working on to darcs and release them.) Regards -- Adrian Hey

On 2006-10-11, Adrian Hey
I don't want to run my own server which provides services people expect in order to use darcs the "normal" way (whatever that might be, I'm afraid I haven't actually used darcs yet, I just want to convert a few libs I'm working on to darcs and release them.)
It literally just requires web-space. If you can get web-space somewhere, it can host a dorcs repository. -- Aaron Denney -><-

Aaron Denney wrote:
On 2006-10-11, Adrian Hey
wrote: I don't want to run my own server which provides services people expect in order to use darcs the "normal" way (whatever that might be, I'm afraid I haven't actually used darcs yet, I just want to convert a few libs I'm working on to darcs and release them.)
It literally just requires web-space. If you can get web-space somewhere, it can host a dorcs repository.
Or maybe even a darcs repository :-) I have web space but was thinking this would not be workable unless darcs supported ftp for writes. Now looking at the docs I see it does, or it says it does for reads in the "Any old server" paragraph, so I suppose it works for writes to? Regards -- Adrian Hey

On 10/12/06, Adrian Hey
Aaron Denney wrote:
On 2006-10-11, Adrian Hey
wrote: I don't want to run my own server which provides services people expect in order to use darcs the "normal" way (whatever that might be, I'm afraid I haven't actually used darcs yet, I just want to convert a few libs I'm working on to darcs and release them.)
It literally just requires web-space. If you can get web-space somewhere, it can host a dorcs repository.
Or maybe even a darcs repository :-) I have web space but was thinking this would not be workable unless darcs supported ftp for writes.
Now looking at the docs I see it does, or it says it does for reads in the "Any old server" paragraph, so I suppose it works for writes to?
(CC'ing darcs-users BTW) Although, I can't speak for this approach myself, I think some people keep a copy of the repository locally and just rsync, unison, ftp, whatever, and transfer the repository back to the server whenever there are changes. This works because people can still send you patches via 'darcs send'. There is also darcs-server (written in perl to enhance server portability) which allows some manner of writting back to the repository via a webserver if I recall correctly (cgi maybe?). HTH, Jason

Hello Adrian, Wednesday, October 11, 2006, 9:39:26 PM, you wrote:
apparently none ghc related projects. Simon M owns/runs the machine and gives out passwords (but I guess you've gotta ask nicely :-) It's not intended to be a general communal darcs supporting sourceforge type place.
But I guess most people already know this.
seems that this is a sort of not very wide-known information :)
So if darcs.haskell.org is not the right place, does anyone have any alternative suggestions?
its name suggests that it the good place for homeless haskell-related projects. anyway we (i mean you and me) asking for place where good haskellers can host darcs repositories for their projects. if this can't be done at darcs.haskell.org nor someone can offer other place, i propose to make directory on regular haskell.org site. something like www.haskell.org/projects and make darcs repositories here. one should just ask for haskell.org account in order to become able to place files here. afaiu now, regular http server is enough to host darcs projects. updates can be send via email to author of each project and applied to our "home" darcs repositories and then propagated to the world by copying all updated files to the haskell.org server
What I was looking for was the appropriate place where that users and be patch contributors could treat as a "one stop shop" for all darcsified projects (and cabalised releases). I.E. same stable URL's, easily browsable and all accessible the same way. I don't want to run my own server which provides services people expect in order to use darcs the "normal" way (whatever that might be, I'm afraid I haven't actually used darcs yet, I just want to convert a few libs I'm working on to darcs and release them.)
if you need just to _release_ it, cabalizing is much more important - it allows one to easily install/compile your lib. darcsing, on the other hand, allow to manage versions, apply patches and so on - i.e. it's more about maintenance and versioning. it don't make much sense for rare releases (or just one release). moreover, its' possible to manage darcs repositories only on local boxes and exchange patches (using email or this mail list) and it will work perfectly fine. public darcs repository is just a place where one can download all the patches instead of scanning, say, mail list well, i just managed myself to read darcs docs at last week and i suggest you to do the same :) http://www.darcs.net/manual/bigpage.html if you need beginners instructions on cabalizing lib - i can help you (anyway i had plan to write such introduction) hackage will be a good place too, but wee need instructions on "hackaging" the lib/app (how many new words! :) and i'm also wondering - can hackage description of package point to the darcs repository (plust tag of concrete version in this repository) ? -- Best regards, Bulat mailto:Bulat.Ziganshin@gmail.com

Adrian Hey wrote:
Hello folks,
These may be dumb questions, but I'm afraid I haven't been keeping up with what's happening in the Haskell world recently..
So..
Is darcs.haskell.org the recommended place to start a new project?
If so, who owns/runs this machine and how do I get access to it?
What's the rationale for it's current organisation e.g. why is there a separate "packages" directory? (There seem to be packages elsewhere) and what's the "packages.hide" directory for?
darcs.haskell.org is physically located at, and run by, the kind folks at Galois. We do give out accounts to people for hosting their darcs repositories, but we're currently looking for a better way to do this. The organisation of the repos is largely accidental: we initially put all the packages that came with GHC under packages/, and then various other library repositories have been created at the top level. Cheers, Simon

Simon Marlow wrote:
darcs.haskell.org is physically located at, and run by, the kind folks at Galois. We do give out accounts to people for hosting their darcs repositories, but we're currently looking for a better way to do this.
I've started a page on the various haskell.org machines: http://haskell.org/haskellwiki/Haskell.org_domain -- Ashley Yakeley
participants (6)
-
Aaron Denney
-
Adrian Hey
-
Ashley Yakeley
-
Bulat Ziganshin
-
Jason Dagit
-
Simon Marlow