On 15/11/2012 09:49, Roland Mas wrote:
But maybe I missed the point, was it said we switch packaging to bzr ?
Not really. I probably should have announced it more loudly than just
on IRC, sorry.
The reasoning for moving the packaging to bzr (from my point of view)
is that:
- I find bzr much saner and simple to use.
- the packaging involves moving files around and renaming them, for
instance the third party JS libraries, and git doesn't really handle
that correctly. Really, seriously, it doesn't.
- Thorsten and I do most of the packaging work these days anyway, and
I'm pretty sure Thorsten prefers bzr too :-)
ok for this, can you tell more about how bzr is synced ?
The one thing I dislike with bzr is that it contains only part of the
repo, (unstable, experimental separated/duplicated branches)
Anyway, I can live with it, I branched the unstable, and experimental,
and now I feel a bit like a chicken in front of a knife ;-)
Got the impression I missed something, any tips ?
I'd like to have the possibility to git clone/push or svn co/commit
the packaging stuffs and to use git in a build bot without having to
deal with bzr
Two different things there: working on the packaging with a git client
should be possible with the appropriate git plugin (the one that nobody
took the time to try when we were evaluating the switch to a DVCS, so
that we eventually switched to git because of inertia rather than
because of good reasons); using git in a buildbot is irrelevant, since
the only way the buildbot should be involved with the VCS is to run
pull/update commands before a build.
I would tend to think these kind of thing is not very reliable, Is it
packaged in some place ?
Christian
_______________________________________________
Fusionforge-general mailing list
[email protected]
http://lists.fusionforge.org/cgi-bin/mailman/listinfo/fusionforge-general
