Le 8 avr. 05, à 06:16, Banlu Kemiyatorn a écrit :
On Apr 8, 2005 1:11 AM, Quentin Mathé
<[EMAIL PROTECTED]> wrote:
Well GNA doesn't support it currently, that's why I was advocating for
Subversion, at least until other SCMs support is added or we move to
our own server.
BTW, do we really need GNA to support Darcs? I was thinking that
just any files repository should be usable, may be we can also store
each darcs' merge in CVS? But actually I just don't want to install a
compiler.
Yep, we don't really need GNA to support Darcs… but that would mean to
have a reliable server where the master copy of the repository is
stored and used to generate sync/commit mails (I really want to have
them).
I don't think Haskell compiler is really a problematic dependency
however.
Last note, for a detailed SCMs comparison :
http://better-scm.berlios.de/comparison/
how about monotone?
I really dislike the hash based visible versioning, otherwise it is
really simple and looks efficient, but I'm bit unsure about it also
because it looks to be still in early development stages, no ?
Darcs seems to be equivalent but more mature, with nice features like
paches commutation model and growing support.
Archipel looks exciting but not written :-D
http://wiki.type-z.org/index.php/Projects/Archipel
Funnily, the guy behind Archipel seems to be working on Objective-C
stuff with Piranhas, on the wiki you can read :
« Piranhas stands for Piranhas is really a new hype agent system, which
is actually not supposed to mean anything. »
hehe
More here : http://wiki.type-z.org/index.php/Projects/Piranhas
Yet another not really coded project it seems. May be Stefan know
something about it ?
There are some interesting comments on Io language on this wiki, a
prototype based object oriented scripting language with Objective-C
integration, but I haven't found time to play with it.
About Io language:
http://www.iolanguage.com
ok.
Have you been able to compile MusicKit with GNUstep ?
That would be cool.
Never.
Ah ok.
I think, you can start to merge in Étoilé cvs, parts of Garma we
discussed in this thread… May be you have some comments or objections
?
Do you want to discuss some points in more details ?
No objection, let me do that after I get diagram kit to work.
ok
I have just seen that Maliwan is using Autoconf, we can keep it for
now, but in future I would like to have it avoided (I just hate
Autoconf :-); I have done some experiments with pmk
<http://pmk.sourceforge.net/> which is quite nice, but it has some
limitations and I still need to figure how to solve them.
I'll maintain them both. garma components must support the GNU way :)
No problem, thanks.
May be we should rename Maliwan to MaliwanKit to keep this "Kit" way
for frameworks ?
Quentin.
--
Quentin Mathé
[EMAIL PROTECTED]
