upload of 0.1.5 done - tagging issues

Adeodato Simó dato at net.com.org.es
Sun Aug 19 09:59:56 UTC 2007


* Stefano Zacchiroli [Sun, 19 Aug 2007 11:37:23 +0200]:

> They are relative to branches, fine.  But I was rather asking for
> relativeness to *directories*. The "x.y.z-a" scheme is ok as long as we
> are maintaining only one source package in our repository, but if
> tomorrow we will go for more than one I guess we will have
> "/trunk/pkg1", "/trunk/pkg2" and so on. That would be (I presume)
> different directories, not different branches. At that point version
> 0.1.0 of pkg1 can clash with the same version of pkg2. ... or I'm still
> missing something here :)

/trunk/pkg1 and /trunk/pkg2 would be separate branches (and would
probably be named pkg1/trunk, and pkg2/trunk, anyway, with pkg1 and pkg2
just being directories (not branches), and trunk and trunk being the
actual branches).

In DVCS, and particularly in Bazaar, one creates a separate branch for
each standalone piece of code, or any piece of code that you may be
interested on checking out separately, instead of aggregating them in a
single branch via subdirectories.

Let me know if everything is clear now. :)

-- 
Adeodato Simó                                     dato at net.com.org.es
Debian Developer                                  adeodato at debian.org
 
                                  Listening to: Carlos Cano - Chiclanera




More information about the pkg-python-debian-maint mailing list