Using bzr-svn and Launchpad

[Alexander Belchenko]

Jelmer Vernooij пишет:
> Eugene Wee wrote:
>> Now, I am not sure how I should get Launchpad to cooperate with
>> Boost's Subversion repository. Should I get Launchpad to import my
>> directory on Boost's Subversion repository? If so, would I be able to
>> bzr push to lp:boost.cgi and have my changes propagated to the Boost
>> Subversion repository? Or would it be better not to use Launchpad for
>> code, and directly bzr push to the Subversion repository instead?
>>   
> If you use Launchpad's vcs-imports service to do the import you can't
> use bzr-svn to push back to upstream; the two aren't integrated (at
> least not yet) and branches created with one aren't compatible with the
> other.
> 
> If lp:boost.cgi is a Launchpad vcs-import of the upstream svn branch you
> won't be able to push to it, it's readonly.
> 
> If you want to contribute back to upstream using "bzr push" your only
> option (so far) is to use bzr-svn to maintain a mirror yourself.
>> Also, are there any pitfalls to watch out for given that I'll be
>> working with Subversion 1.4.2? Like, should I use bzr dpush, or would
>> bzr push be fine? What about the new EOL handling that I understand
>> works with bzr-svn 0.5.4?
>>   
> The EOL property is only picked up in native Subversion working copies,
> not in Bazaar branches (as there is no way to store svn file properties
> in bzr branches/working trees). In native Bazaar branches you can still
> have eol handling, but you'll need to configure it manually (in
> ..bzr/branch/rules or ~/.bazaar/rules).

Note: .bzr/branch/rules does not work yet.

> 
> bzr push and bzr dpush will both work fine; you'd probably want to use
> dpush only if the remote Subversion repository is running Subversion <
> 1.5 *and* you don't want bzr to set custom file properties.
> 
> Hope this helps,
> 
> Cheers,
> 
> Jelmer
> 
>