bzr should have option to disable foreign workingtree support

Bug #476252 reported by INADA Naoki on 2009-11-06
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Wishlist
Unassigned

Bug Description

I want to use bzr-svn for branching from svn repository.
But I don't want to use bzr for svn workingtree for two reasons.

1. Sometimes I use bzr and svn like below:
$ svn co http://svn.example.com/readonly_proj/trunk
$ bzr init
$ bzr ignore .svn
$ bzr add
$ bzr commit
...

2. When TortoiseBZR loads bzr-svn plugin, TortoiseBZR and TortoiseSVN conflicts.

Jelmer Vernooij (jelmer) wrote :

This is something that should be handled in Bazaar itself, the same issue would come up for bzr-git and bzr-hg.

affects: bzr-svn → bzr
summary: - bzr-svn should have option to disable svn workingtree supprot.
+ bzrshould have option to disable foreign workingtree support
Changed in bzr:
status: New → Triaged
status: Triaged → Confirmed
importance: Undecided → Wishlist

Also note that in the specified situation you can use "bzr --no-plugins init" to avoid bzr-svn from being loaded.

summary: - bzrshould have option to disable foreign workingtree support
+ bzr should have option to disable foreign workingtree support

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

Jelmer Vernooij wrote:
> Also note that in the specified situation you can use "bzr --no-plugins
> init" to avoid bzr-svn from being loaded.
>

Note, though, that whenever you tried to work in a subdirectory, it
would fine the .svn directory before it would fine the containing .bzr
directory.

svn would also be special in this, versus .git and .hg. As such, I'm
pretty sure we probe for .bzr before the rest, which means that if
someone did "bzr init --no-plugins" then it would work as expected for
bzr-git and bzr-hg, but *not* for bzr-svn.

John
=:->

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

iEYEARECAAYFAksBgGEACgkQJdeBCYSNAAN+IACcCmLD57S6/t8qPQyp540V9LQU
EegAn01N4r44JsHkIDC6Rh6rsg2VXqJL
=lSrJ
-----END PGP SIGNATURE-----

Jelmer Vernooij (jelmer) wrote :

Hi John,

On Mon, 2009-11-16 at 16:40 +0000, John A Meinel wrote:
> Jelmer Vernooij wrote:
> > Also note that in the specified situation you can use "bzr --no-plugins
> > init" to avoid bzr-svn from being loaded.
> Note, though, that whenever you tried to work in a subdirectory, it
> would fine the .svn directory before it would fine the containing .bzr
> directory.
>
> svn would also be special in this, versus .git and .hg. As such, I'm
> pretty sure we probe for .bzr before the rest, which means that if
> someone did "bzr init --no-plugins" then it would work as expected for
> bzr-git and bzr-hg, but *not* for bzr-svn.
I'm not sure I follow - how could bzr-svn be involved if somebody ran
--no-plugins ?

You would run into similar issues with git or hg if you were trying to
init a bzr branch in a subdirectory of a git or mercurial repository.

Cheers,

Jelmer

--
Jelmer Vernooij <email address hidden> - http://samba.org/~jelmer/
Jabber: <email address hidden>

Jelmer Vernooij (jelmer) on 2017-11-09
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers