On 2016-05-25 09:25:08, Joachim Breitner wrote: > Hi, > > Am Mittwoch, den 25.05.2016, 08:25 +0200 schrieb Stefano Zacchiroli: > > I just wonder whether we should also take the chance of improving the > > spec in a way that will allow, down the line, to automatically find the > > actual packaging code also in other, more complex situations. Specifying > > a branch is the first thing that comes to my mind. But we have seen in > > the past that it might also be useful to be able to specify the given > > layout of the Git repository (i.e., is it a debian/ only, is it split > > debian/upstream, is it merged debian/upstream, etc). > > > > All this considering, here are a few options: > > > > 1) URL [DIR] <- what you suggested > > > > 2) URL [dir=DIR] > > > > where "dir" is an actual string, in keyword-argument style, that > > makes it explicit what the extra optional argument means. This would > > allow in the future to have other extra arguments without creating > > ambiguity. This would allow something like the following: > > > > 3) URL [dir=DIR] [branch=BRANCH] [layout=LAYOUT] > > There is precedent here, namely "-b branch", which is already > supported. The reason this syntax is there is because git understands > it out of the box, but that does not stop us from using it for other > fields as well, e.g. "-d directory", > "-l layout" etc.
So basically the question is between 1) and 2), and if we do 2), what kind of syntax to use (either "dir=path/to/package" or "-d path/to/package"). Since option 1) is restrictive (doesn't allow expansion), and option 2) with "-x foo" is along what we already have, I propose that for now: - we add "-d path/to/project" (debcheckout, vcswatch, policy, etc.) - document that the list of options can be extended in the future (policy) And we leave the discussion of repository layout (native, debian/ only, etc.) for another time. Yay/nay? thanks, iustin
signature.asc
Description: PGP signature
