export over ftp.

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

DeeJay wrote:
> On 13 February 2010 17:52, Eric Berry <elberry at gmail.com> wrote:
>> Hi DJ,
>>
>>> Just a suggestion that you might find it easier to interact by asking
>>> this question
>>> HERE > https://answers.launchpad.net/bzr - but I'm sure people will help
>>> on this
>>> list if they can.
>> Thanks, and sorry. :) I will remember to use the LP answers in the future.
>>
> 
> It was suggestion, not a commandment or reprimand. What Martin says in
> this respect is definitive.
> 
>>> You don't say what bzr operations you have actually tried - can you give
>>> the
>>> command you issued?
>> I was using bzr export. I was hoping I could simply export my project to a
>> remote directory on FTP. I know you can push changes to a branch hosted
>> through FTP.
>>
> 
> I get the same error.
> 
> It isn't clear from 'bzr help export' whether the DESTINATION
> semantics can deal with a URL referring to a remote system, or whether
> the export can only be to the local system.
> 
> Because of the error we both see I suspect the latter - can anyone
> more familiar with code confirm, please?
> 
> DJ
> 
> 

'bzr export $PATH' only works with local filesystems at this point.

You may want to investigate 'bzr-upload' which is also smart enough to
be able to update a remote site without having to copy all of the content.

It probably wouldn't be a lot of effort to allow a URL to $PATH, but it
is unclear if it is actually worthwhile. 'bzr-upload' provides a much
better use case for uploading to an ftp site, etc.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkt3KXYACgkQJdeBCYSNAAMhcgCePLqwxLyU35y3+q3Lg105OZBE
h44AniFpjyxeobBdio9COB3SjYaj4eAi
=AHb+
-----END PGP SIGNATURE-----