On 9/7/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > On 7 Sep 07, at 5:20 PM 7 Sep 07, Brian E. Fox wrote: > > > I don't currently, but have in the past used file:// for remote. > > > > For deploying or actually pulling? Deploying is a totally different > story. I know tons of people who use file, dav, scp, and ftp. > Strictly for pulling I'm saying. And I'm not saying it will satisfy > our users, just throwing out the idea. But HTTP is pretty much > ubiquitous, handles all security concerns, easily distributed ...
I've used file:// it many times this year to ensure that a set of artifacts delivered as "remote" repository contents actually contains everything needed to build, and for testing pre-release artifacts locally that we don't want to put in the internal corporate repo just yet. And it has applications for a 'self contained' project where the repository is packaged with the source code, and builds against those artifacts with no access to external repositories. Losing file:// would be a pain; the others I can live without. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
