Re: [ jEdit-devel ] RFC: Support to host plugins using other SCM besides SVN.

[Eric B. <el...@gm...>]

Shlomy Said:

The entire history of the repository is stored locally????? That
would, sort of, end my local disk space, which means I would not even
start using it.

I just took a couple of hours, and imported jedit/trunk into a local bzr
branch:
 36M    ./bzr_repo
 32M    ./clean_trunk

The clean_trunk is a fresh checkout of jedit/trunk from svn. The bzr_repo is
a bzr repository with one branch inside it.

Just for fun, I then created another bzr branch from the trunk branch inside
the bzr repo.

 50M    ./bzr_repo
 32M    ./clean_trunk

So it added roughly 14M to the repository size?

This is what's inside the bzr_repo directory:
 13M    ./bzr_trunk
 13M    ./test_branch

Each checkout of jEdit trunk, or any other jEdit branch from SVN will equal
32M, so for each branch you create, you save about half.

BTW, one added benefit, is that I can now push my local bzr branch to any
bzr hosted repository for easy server migration. :)

On Mon, Aug 17, 2009 at 6:30 AM, Dale Anson <da...@gr...> wrote:

> While I have nothing against either Bazaar or Git, I think allowing each
> plugin to have a (possibly) different SCM will cause two problems:
>
> 1.  It means the plugin builder will need to have the tools and
> knowledge to support all of these SCM systems.  This only affects a
> handful of people, so maybe this isn't a large problem.


This one isn't that big of an issue. The ant scripts I've created already
work with SVN, Git, and Hg, I just haven't gotten around or had a reason to
add support for Bazaar yet.


>
> 2.  It will make it harder for other developers to contribute since they
> too will have to have the tools and knowledge to support these systems.
>
> I have found that projects that use Maven rather than Ant have the same
> issues.  It is a lot of work to set up Maven for the first time (it's a
> fairly large install), just to get a developer to the point where they
> can help out with a small bug.  Personally, I'd like to keep the
> barriers to entry low to increase the possibility of help.  People who
> might prefer to use Bazaar or Git probably already have experience with
> SVN, but the converse is not as likely.
>
> I'm not sure I see the real issue. This only becomes a problem when plugins
have dependencies on other plugins not in their SCM, and it really only
becomes a problem when the developers need up-to-date, HEAD/TRUNK
development of those dependencies. Otherwise, they can always get the source
with the plugin binary through PluginManager.

Regardless though, I get the feeling it would be more of a headache than
it's worth. :) I definitely didn't want to add more confusion to the mix.
Perhaps it's better to perfect the current processes first before other SCMs
are looked into?

-- 
Learn from the past. Live in the present. Plan for the future.
11101000
http://www.townsfolkdesigns.com/blogs/elberry