On Thu, 15 Nov 2012, Christian Bayle wrote: > But maybe I missed the point, was it said we switch packaging to bzr ?
We did not say anything about how packaging would be managed, at all. But it does indeed make sense to use the same VCS as upstream, if it’s a DVCS, to be able to easily import upstream code into a branch and branch off that the debian/ branch. (See the Bremner talk at DebĆevapčićiConf about git packaging. Not that this doesn’t work just as well with CVS, I’m doing that, but in the git model, everyone can just take the upstream code and pull/push it. That being said, there _is_ an “official” (and imported by Launchpad) FusionForge bzr location, from which we can probably pull.) Considering that we did not do a final, “no way back” decision to use git in FusionForge itself, I don’t really see a problem with using bzr for the packaging. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-314 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Boris Esser, Sebastian Mancke _______________________________________________ Fusionforge-general mailing list [email protected] http://lists.fusionforge.org/cgi-bin/mailman/listinfo/fusionforge-general
