[MERGE] bzr.exe: move builtin plugins out of library.zip todirectory 'plugins'

[Alexander Belchenko]

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

Robert Collins пишет:
| On Tue, 2008-01-29 at 19:31 -0800, Wichmann, Mats D wrote:
|> bazaar-bounces at lists.canonical.com wrote:
|>> On Tue, 2008-01-29 at 22:43 -0200, Martin Albisetti wrote:
|>>> On Jan 29, 2008 10:21 PM, Robert Collins
|>> <robertc at robertcollins.net> wrote:
|>>>> I think this is a bad idea; the plugins shipped with bzrlib are in
|>>>> lockstep with bzr itself, and having them separate on disk allows
|>>>> many opportunities for problems.
|>>> A few users have already dropped into #bzr wanting for some easy way
|>>> to remove bundled plugins (specifically the Launchpad one), and
|>>> having them in a zip file will complicate the implementation of
|>>> Automatic Plugin Managment[1].
|>>>
|>>> How is this done in OSX?
|>> The automatic plugin management stuff should not touch built in
|>> plugins. They are not truely independent - e.g. bundles /depend/ on
|>> those plugins being present and of the correct version.
|> But not on the Launchpad plugin, I assume?
|
| The launchpad plugin is truely a plugin - optional extension that we
| ship with bzr; the the multiparent plugin is not - if its not present
| then errors will occur in non obvious places.

In this case it should be in the bzrlib core.
Either multiparent is plugin or it's the part of core.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHoADCzYr338mxwCURAkw6AJ9MJLLnw64hH16tcv7zBb02E62zWACffxrx
ET/vWZ7yKx6dcXoMFlXqqRs=
=P75J
-----END PGP SIGNATURE-----