Thomas Zander wrote:
the challenge here is with integrity of the archive. now maybe this is
different with the Web space but the last time I used source for for
this (IPCop wiki), we had major problems with unauthorized people
deleting our site.
The http part is for public downloads; the ssh part for private uploads.
Nobody that does not have a ssh account can alter your site.
this is the very point I was making anyone with an SSH account can
modify your site. As far as I know based on the vandalism I have seen.
Obviously if they have changed things, that's great.
I do this on my sourceforge site; see:
http://uic.sf.net/_darcs/
where you can dargs get http://uic.sf.net
and if you are in the project (which , at unix level means in the right
group) you can write using ssh.
darcs push uic.sf.net/home/groups/u/ui/uic/htdocs/
I noticed you use CVS on that site instead of advertising darcs?
The patches come in via my normal email program. See the darcs manual for
several methods to use sended patches and get them incorporated into the
archive.
I'm sure there is one for you.
I've read the manual many times over the past year(?)or so and the basic
mechanisms for propagating patches are one of the biggest weaknesses for
usability in darcs. if my hands weren't so broken, I would probably put
in a plug-in mechanism to any transport for patches. I suspect the
easiest way would be to leverage the infrastructure found in the SMTP
transport and just make the transport mechanism variable. So for
example one could use an xmlprc interface to a repository or even a
simple http multipart upload with a CGI chaser.
I was talking with some people on IRC last night and the SMTP based
patch feed does have some charms in a source forge like environment if
you assume that patch is only come from trusted people and do not go
through some human process on the front-end.
The manual explains a pgp-signature approuch, among others. Please do read
the manual.
yes,that's what made me think it was possible and even desirable.
I suggest the first setup I described at the top of this email. Use
sourceforge and ssh.
Oh; I did place a darcs executable in my personal account homedir and
altered my .bashrc to put that in my path. Just ask if you are stuck.
ah. interesting. The FAQ says
http://darcs.net/DarcsWiki/FrequentlyAskedQuestions#head-d5a5bbdfabe810765004987ace054cb5e90e9ab8
...
it is possible to upload a darcs binary to your SourceForge shell
account, but it may be a breach of your user agreement with Sourceforge
...
maybe we (the darcs community) should pick on one of the project
repository sites, and see if we can get them to modify their environment
to support darcs. I suspect Savannah might be the best for this because
they desperately need volunteers to help and volunteers get what they
want (usually)
(no, I'm not volunteering for anything additional. My life is too full
as it is :-)
---eric
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
