Package: dgit
Version: 3.4
So far, dgit tries to determine the distro from the suite name. This
approach relies on suite names being unique across distros.
This is not true: for example, it is often not true for Debian
derivatives which roughly share Debian's release schedule.
Such a distro should have separate suite branch names, at least.
There is a decision to be made on what the format of that branch name
should be. [1]
Then we need to go through the code in dgit and ensure that the suite
name is appropriate qualified everywhere. Probably, $csuite needs to
be abolished and turned into two variables, one containing the distro
name and one being just the bare suite.
There should be separate a config option (separate to
dgit.default.distro) to specify which distro(s) distro-unqualified
branch names refer to. This config option mustn't change often,
because changing it can change the implied upstream source of a branch
name.
[1] Sane possibilities for the branch name would appear to include
(opinions welcome):
My favourites:
Format (local branch) Example
dgit/DISTRO=SUITE raspbian=jessie
dgit/DISTRO#SUITE raspbian#jessie
dgit/SUITE@DISTRO jessie@raspbian
Other possibilities:
dgit/DISTRO%SUITE raspbian%jessie
dgit/SUITE%DISTRO jessie%raspbian
As for the other possible delimiters:
/ might cause trouble if any distro had the same name
as a suite, and produces names of varying depths
(does this matter?)
_ . - + seem like they might appear in distro or suite names
and so would be ambiguous, which is no good here
since dgit will need to parse the combined name
, used already for the multisuite syntax
: ~ ^ forbidden by git
! " $ & ' ( ) * < > ; ? [ ] \ ` { } |
shell metacharacters
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
