Distributed model for bundles (was: [TxMt] Bundle and language help)

[Sebastian Gräßl]

I think it is not a good idea to switch to a distributed model for  
the Bundles.
There are just 36 Bundles out of 152 which are really official and  
get shipped with TM, the others are optional.
The way to go is not to switch the source control system. We should  
think about the distributing process.
I think there should be no source control information in the Bundles  
the user installs.
I think we should let decide each maintainer what he wants to use and  
just give a solution to make the bundle public.
A small web app would do the trick.

There could be two options for a Bundle maintainer:
1) i have no source control... i upload ZIP's
2) i have svn (or what ever)... please checkout/export my source when  
i ping you with a special token and zip it for me. (the ping could be  
done by a simply hook or manualy)

The client side should be no problem because i think most ordinary  
users use the GetBunlde and to switch the installing and updating  
process will be no problem. The version control will be don be the  
web app.
Also it should be possible to give the Bundle a status like "beta",  
"use at your own risk"...

Basti



On 06.08.2007, at 19:40, Gerd Knops wrote:

>
> On Aug 6, 2007, at 12:11 PM, Allan Odgaard wrote:
>
>> On 6. Aug 2007, at 17:10, Jeremy Wilkins wrote:
>>
>>> Without wishing to turn this into a which scm is best discussion,  
>>> git isn't the easiest system for non-technical users to learn -  
>>> it is aimed at power users. You may end up with a situation where  
>>> using the version control is harder then creating the bundle.  
>>> I've not used mercurial much but I know thats meant to be simpler  
>>> than git, I have used bzr which i've found dead simple and quite  
>>> like subversion, and it branches happily from subversion. I'm  
>>> sure theres other possibilities.
>>
>> I was careful not to mention any system in particular :)
>>
>> Git from a usability POV is indeed frustratingly (and  
>> unnecessarily) complex.
>
> I have been using darcs for a while, and when it works it is quite  
> cool. It can be used concurrent with svn (eg use both darcs and svn  
> on the same tree) and is rather easy (almost intuitive) to use.
>
> But it has two rather big drawbacks:
>
> 1. It is written in Haskell, and getting Haskell to run on OS X is  
> slightly trying.
> 2. If you ever browse it's directory (_darcs, so not hidden) with  
> the Finder, it chokes badly on any .xxx files the Finder may leave  
> behind.
>
> Gerd
>
>
> ______________________________________________________________________
> For new threads USE THIS: textmate at lists.macromates.com
> (threading gets destroyed and the universe will collapse if you don't)
> http://lists.macromates.com/mailman/listinfo/textmate