Hi all, I've been talking to Erik Enge on #lisp and suggesting to go into full support mode for arch. (-: What is left to do: not much, really. development of arch-based projects on common-lisp.net is possible already, as both non-anonymous ftp and anonftp are supported. What would be good to have: a few things. * sftp support for people who are reluctant to transmit passwords in plain text over the net. this will probably also benefit users who don't use arch. * no delay between uploading something and it appearing in the anonftp download area. Would it be possible to upload to the download area directly? Erik said it was a permission problem. That should be easily fixed, I guess (-: Erik also asked about a script to send notifications to project mailing lists when a change get committed to the arch archive. This is a little harder to implement, but should be doable via the "dnotify" agent. I'll look into that when I have the time. Anyway, thanks for putting up common-lisp.net! Good night, -- Andreas Fuchs, <asf@acm.org>, asf@jabber.at, antifuchs
Slightly off topic, but I'd like to hear what you think of Arch. I've been using subversion for a while and it's definitely an improvement over CVS. I've just started looking at arch and it seems interesting but a bit more difficult to learn for a CVS user. On Tue, 2003-08-19 at 12:11, Andreas Fuchs wrote:
Hi all,
I've been talking to Erik Enge on #lisp and suggesting to go into full support mode for arch. (-:
What is left to do: not much, really. development of arch-based projects on common-lisp.net is possible already, as both non-anonymous ftp and anonftp are supported.
What would be good to have: a few things.
* sftp support for people who are reluctant to transmit passwords in plain text over the net. this will probably also benefit users who don't use arch. * no delay between uploading something and it appearing in the anonftp download area. Would it be possible to upload to the download area directly? Erik said it was a permission problem. That should be easily fixed, I guess (-:
Erik also asked about a script to send notifications to project mailing lists when a change get committed to the arch archive. This is a little harder to implement, but should be doable via the "dnotify" agent. I'll look into that when I have the time.
Anyway, thanks for putting up common-lisp.net!
Good night, -- Miles Egan <miles@caddr.com>
Miles Egan <miles@caddr.com> writes:
Slightly off topic, but I'd like to hear what you think of Arch. I've been using subversion for a while and it's definitely an improvement over CVS. I've just started looking at arch and it seems interesting but a bit more difficult to learn for a CVS user.
Even more off topic, if you would like to have Subversion access on common-lisp.net, put together a short list of things for me to do and I'll set it up. (I'll do it on my own but it will take some time as I'll have to learn SVN first.) Erik.
On Tue, Aug 19, 2003 at 04:30:36PM -0400, Erik Enge wrote:
Even more off topic, if you would like to have Subversion access on common-lisp.net, put together a short list of things for me to do and I'll set it up. (I'll do it on my own but it will take some time as I'll have to learn SVN first.)
On topic ;) I think that once we add Arch & Subversion support we need to rethink some things about how new projects are handled, since it could be a little confusing for projects to have both svnroot and cvsroot... My though: projects tell what features they wish to use on in their hosting application. The appropriate directories and mailing lists get created + public_html (with a default index.html that includes the description the project gave on application). Eg: Application for mailing-list lispgui. Just public_html and list lispgui-devel get created. Not ftp, no nothing. Later they may decide that they need other features well -- when so, then so. Application for foo, with Subversion and ftp. They get foo-devel, foo-svn, and in their dir they have public_html, svnroot and ftp. Too involved? Sort of ok? Cheers, -- Nikodemus
Nikodemus Siivola <nikodemus@random-state.net> writes:
On topic ;) I think that once we add Arch & Subversion support we need to rethink some things about how new projects are handled, since it could be a little confusing for projects to have both svnroot and cvsroot...
Well, yes, but only from the requesters point of view. Underneath, they are all shell scripts to do the individual jobs. Perhaps a neat little HTML form with dropdowns etc. could do the trick. I want to be able to say: * (make-project :name "my_project" :revision-control :cvs :owner "eenge") => #<PROJECT {234234}> and then probably something like * (store-in-database *) and that's the end of that.
Too involved? Sort of ok?
I think everybody should get ftp, public_html and webspace by default. Revision control needs to be selected (once we offer more than one option). Erik.
common-lisp.net and arch: 1) getting sftp access up requires no modifications to common-lisp.net's current setup. i am currently using an archive in /project/bese/bese-devel@common-lisp.net. 2) for anonymous access (read-only) it would be sufficent to symlink each project's archive directory to the wwwroot of the project. In this setup each project that uses arch would have one public read-only archive: http://common-lisp.net/project/PROJECT-devel@common-lisp.net and, for write access: sftp://DEVELOPER@common-lisp.net/project/PROJECT-devel@common-lisp.net why arch rocks CVS' world: [i've never tried subversion or darc or bitkeeper, just CVS.] 1) branching and merging is EASY. I find myself makes lots of branches just so that i can just "try stuff out"; then merging if i decide it works. 2) renames, symlinks, directories are handled as they should. 3) changesets as opposed to single file versions. 4) local archives which mirror remote archives, each local archive is a new branch, so you can commit all you want. merging does not lose the patch history. 5) using sftp allows me to install it on any machine i want. 6) any revision can be checked and used as a complete tree (go back four versions, edit, merge, continue). I have one major gripe: it imposes a (for me) weird naming scheme in order to distinguish files under revision contral as opposed to other files (ie it's missing .cvsignore (but you con fake it, sorta)). -- -Marco Ring the bells that still can ring. Forget your perfect offering. There is a crack in everything. That's how the light gets in. -Leonard Cohen
participants (5)
-
Andreas Fuchs -
Erik Enge -
Marco Baringer -
Miles Egan -
Nikodemus Siivola