Dave, Thanks for the suggestion. It also occurs to me that Pharo *has* to contain the upload code, so I might simply be able to isolate and script it to push only what I specify. I just need an idiot proof safe solution.
Bill ________________________________________ From: pharo-project-boun...@lists.gforge.inria.fr [pharo-project-boun...@lists.gforge.inria.fr] on behalf of Dave Mason [dma...@mason-rose.ca] Sent: Sunday, February 05, 2012 8:41 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Alternative to MC for upload? On 2012-Feb-5, at 8:13 , Schwab,Wilhelm K wrote: > The only thing you are missing is that I (presumably) made a mistake that > once broke a barrier between public code and things that I had not intended > to release. The "spill" was code that was not worthy of release (otherwise > harmless), but it could have just as easily have been something that is > "somebody else's intellectual property." It is that latter mistake that I > don't ever want to make, so I would like to be specific about the files I > push. I thought you should be able to access www.squeaksource.com using WebDAV, but at least guest access doesn't work. There must be one of the protocols that WebDAV uses that the monticello server that I presume powers ss doesn't support, because the converse certainly works, I have a local WebDAV that MC is quite happy with. If you had webdav you could move over files (and possibly delete old files you didn't want there). ../Dave
