On Sat, 2007-07-07 at 10:53 -0400, seth vidal wrote: > On Sat, 2007-07-07 at 10:39 -0400, Jesse Keating wrote: > > > 4. essentially this box will be for rsync/scp/sftp of files to a place > > > where everyone can get to. Is there any other package that should be on > > > here? > > > > git would be nice, with the git server setup so that people can easily sync up > > a git repo to there or push via ssh to there and other people can get to it > > with git:// > > > > Hg is harder and maybe not possible. > > Isn't the above what rsync is for? I guess I'm inclined to not have any > scm - this is just a big box which serves files, statically, and does > not open us up to that many attack vectors. If we allow these, I'd also like to request bzr :-) git, hg, and bzr can all be served directly over http. I believe that either sftp or rsync push is supported by all of them as well. having a server has several advantages: 1) Faster. The server can optimize what it sends over the wire so there's less data to transfer. Also, it can perform some pieces of a command on the server and send only the results. 2) Online browsing. In some cases the server has a web interface built in that makes it easy to view the source online. 3) Other features. I don't know what other features exist for hg and git (bzr is only about performance ATM) but things like repository specific ACLs need server-side support to work (could be done with fs ACLs if we have the ability to shell in.) With that explanation out there, I think I'm inclined to agree with Seth. Let's keep fedorapeople simple unless we find our needs are simply too big. We might want to provide some client-side scripts to aid in working with fedorapeople, though. For instance, a script that maintains a yum repo clientside and rsyncs it to fedorapeople would be nice. -Toshio
Attachment:
signature.asc
Description: This is a digitally signed message part
