tag:blogger.com,1999:blog-4667186581055843327.post3550025426189427075..comments2023-06-01T10:38:03.832+02:00Comments on DVCS Comparison: Plugins in Version Controlaoeuohttp://www.blogger.com/profile/18078968458776470061noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-4667186581055843327.post-37991844365271447652010-09-05T00:22:53.246+02:002010-09-05T00:22:53.246+02:00Who's going to install them, you ask? For most...Who's going to install them, you ask? For most of those, the answer probably includes the typical Windows user: going by "bzr plugins", mine (2.1.1) came with:<br /><br /> * bzrtools 2.1.0<br /> * explorer 1.0.1 (Bazaar Explorer)<br /> * launchpad 2.1.1 (in-tree)<br /> * netrc_credential_store 2.1.1 (in-tree)<br /> * news_merge (in-tree)<br /> * qbzr 0.18.4<br /> * rebase 1.0.2<br /> * svn 1.0.2<br /> * upload 1.0.0dev<br /> * xmloutput 0.8.7.dev<br /><br />I don't recall if the default was to install all of them or not, but it certainly wasn't discouraged at all.<br /><br />Now if only Cygwin had even <b>half</b> of these plugins packaged (not counting the in-tree ones)...<br /><br />It certainly would be nice if there was more integrated documentation and a websites each could belong to, but oh well. The decent subversion integration & UI were all it took to win me over :-).SamBhttps://www.blogger.com/profile/06560268240719951351noreply@blogger.comtag:blogger.com,1999:blog-4667186581055843327.post-27334925463955313582008-06-25T16:29:00.000+02:002008-06-25T16:29:00.000+02:00Well then your distribution can also manage Mercur...Well then your distribution can also manage Mercurial extensions for you :-) How many people install Mercurial from the original download site (excluding Windows people, but for them there is even a custom exe with some stuff enabled)?<BR/><BR/>Also, I think extensions can harm ease-of-use if they are all enabled by default. For example, "hg help" on a vanilla install will give you the set of core commands. If you add e.g. mercurial queues, and perhaps a couple of other extensions, the list of commands will be much more crowded.<BR/><BR/>Endly there are extensions like "highlight" (syntax highlighting in the Web view) which are preferably disabled by default as they eat a lot of resources.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4667186581055843327.post-29332561090010540032008-06-25T12:06:00.000+02:002008-06-25T12:06:00.000+02:00@Last anonymous:Sure, they might be included, but ...@Last anonymous:<BR/><BR/>Sure, they might be included, but the point still stays, as you have to activate them first. If it's just for Mercurial developers to separate stuff, why not activate them by default? Having to activate plugins gives a sense of of doing something that is not fully supported, just like going to Mozilla with your FireBug problems.<BR/><BR/>The kernel may have it's modules, but as an end-user you don't have to see them, as you use a distribution that manages all that stuff for you.Pieterhttps://www.blogger.com/profile/12746479461303322910noreply@blogger.comtag:blogger.com,1999:blog-4667186581055843327.post-68884445760095552362008-06-25T12:02:00.000+02:002008-06-25T12:02:00.000+02:00Actually, Mercurial has official built-in plugins....Actually, Mercurial has official built-in plugins. See <A HREF="http://www.selenic.com/mercurial/wiki/index.cgi/UsingExtensions" REL="nofollow">Extensions bundled with Mercurial</A>.<BR/><BR/>The notion of a plugin (or extension) exists in order to decouple the core functionality and stuff which is either peripheral, optional, or even cosmetic. Even the Linux kernel has modules you know :-)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4667186581055843327.post-71297310226717671692008-06-23T22:59:00.000+02:002008-06-23T22:59:00.000+02:00"On the other hand we have success stories of Fire..."On the other hand we have success stories of Firefox extensions"...<BR/><BR/>...but see also <A HREF="http://www.codinghorror.com/blog/archives/001077.html" REL="nofollow">Coding Horror: The Dark Side of Extensions</A> by Jeff Atwood (from March 18, 2008)Jakub Narebskihttps://www.blogger.com/profile/11847202568800326989noreply@blogger.comtag:blogger.com,1999:blog-4667186581055843327.post-43769404696315294702008-06-23T13:04:00.000+02:002008-06-23T13:04:00.000+02:00On the other hand we have success stories of Firef...On the other hand we have success stories of Firefox extensions, Perl CPAN modules, Emacs packages,... Both Bazaar and Mercurial provide semi-official directory of plugins.Jakub Narebskihttps://www.blogger.com/profile/11847202568800326989noreply@blogger.comtag:blogger.com,1999:blog-4667186581055843327.post-31621919664378069192008-06-22T20:23:00.000+02:002008-06-22T20:23:00.000+02:00Exactly. A couple of weeks ago I tried to evaluate...Exactly. A couple of weeks ago I tried to evaluate how good Bazaar's bzr-svn plugin is as an Subversion client. I still don't know because I couldn't get it working due to some dependency problems. Seems like I have too old Python version (or something). It also seems that bzr-svn needs different repository format than the default one in bzr. Doesn't sound like a "works by design" approach to me. And I was just trying to <I>evaluate</I> the tool.<BR/><BR/>Yes, plugins are nice for users for hacking minor personal convenience improvements but there's a real problem if anyone's workflow starts to rely on some functionality only provided by third-party plugins. Then it's clear that the core tool is lacking some important features.Anonymousnoreply@blogger.com