Guido Günther writes ("Re: git, debian/ tags, dgit - namespace
proposal [and 1 more messages]"):
> On Mon, Nov 16, 2015 at 03:11:54PM +0100, Stefano Zacchiroli wrote:
> > You're absolutely right in being unwilling to use "dgit" as part of the
> > namespace, on t
On 2015-11-16 13:27:33, Ian Jackson wrote:
> [resending because my MUA messed up]
>
> Ben Hutchings writes ("Re: git, debian/ tags, dgit - namespace
> proposal"):
> > Deliberately creating identifiers that differ only by case seems
> > gratuito
Hi,
On Mon, Nov 16, 2015 at 03:11:54PM +0100, Stefano Zacchiroli wrote:
> On Mon, Nov 16, 2015 at 02:02:32PM +, Ian Jackson wrote:
> > I'm considering:
> >archive/{debian,ubuntu}/
> >{debian,ubuntu}/archive/
> >
> > I'm still considering the capitalisation idea.
> >
> > Other
On Mon, Nov 16, 2015 at 02:02:32PM +, Ian Jackson wrote:
> I'm considering:
>archive/{debian,ubuntu}/
>{debian,ubuntu}/archive/
>
> I'm still considering the capitalisation idea.
>
> Other suggestions welcome.
More of a meta-idea.
You're absolutely right in being unwilling to use
Ian Jackson writes ("Re: git, debian/ tags, dgit - namespace proposal
[and 1 more messages]"):
> Colin Watson suggested (in pers.comm)
>pkg/debian/
> This is better but it still has a problem with collate order.
>
> It may seem a petty thing to worry about, but fo
[resending because my MUA messed up]
Ben Hutchings writes ("Re: git, debian/ tags, dgit - namespace
proposal"):
> Deliberately creating identifiers that differ only by case seems
> gratuitously confusing.
I acknowledge that this is a downside of my proposal. However, it
Daniel Reurich writes ("Re: git, debian/ tags, dgit - namespace
proposal [and 1 more messages]"):
> "archive" is rather indescript and confusing too.
Sadly there's not space for an essay, and the underlying situation
(particularly, the existing use of the DEP-14 namespac
Barry Warsaw writes:
> On Nov 16, 2015, at 04:52 PM, Ian Jackson wrote:
> >I'm leaning towards
> > archive/{debian,ubuntu,...}/
> >
> >This is on the grounds that the tag's semantics are that the source
> >code referenced by the that is what is in the specified distro
> >archive, under the
On Nov 16, 2015, at 04:52 PM, Ian Jackson wrote:
>I'm leaning towards
> archive/{debian,ubuntu,...}/
>
>This is on the grounds that the tag's semantics are that the source
>code referenced by the that is what is in the specified distro
>archive, under the specified version number.
LGTM, and I
On 17/11/15 05:52, Ian Jackson wrote:
Guido Günther writes ("Re: git, debian/ tags, dgit - namespace proposal
[and 1 more messages]"):
On Mon, Nov 16, 2015 at 03:11:54PM +0100, Stefano Zacchiroli wrote:
You're absolutely right in being unwilling to use "dgit" as p
Ian Jackson writes:
> It has nothing to do with the source format. That's the opposite of
> what this tag namespace is for. For a package and version this git
> tag refers to the source code that you'd get out of `apt-get source'
> or dpkg-source -x,
Hi,
On Sun, 15 Nov 2015, Ian Jackson wrote:
> * A request for anyone to say if they know of a reason I shouldn't do
> this.
I have to agree with Ben. A namespace differing only by the case
is not very helpful.
In DEP-14 we have already "debian/patches/" for the upstream
branch with Debian
On 16/11/15 22:57, Brian May wrote:
> In what way does your use differ from the debian/ tag in
> DEP-14?
For a 3.0 (quilt) package, debian/1.2.3-4 is whichever the maintainer
finds most useful for their particular workflow, either "patches
applied" or "patches unapplied". The version with patches
Currently, the debian/ git tag namespace is used by a number
of different tools, and can mean different things in different
packages and sometimes even different things for the same package in
different repos or trees.
dgit produces, and the dgit git server requires, tags of this form,
which
On Sun, 2015-11-15 at 21:10 +, Ian Jackson wrote:
[...]
> So this message is:
>
> * A request for anyone to say if they know of a reason I shouldn't do
> this.
[...]
Deliberately creating identifiers that differ only by case seems
gratuitously confusing. Further, it may cause difficulties
On 2015-11-15 21:26:52, Ben Hutchings wrote:
> On Sun, 2015-11-15 at 21:10 +, Ian Jackson wrote:
> [...]
> > So this message is:
> >
> > * A request for anyone to say if they know of a reason I shouldn't do
> > this.
> [...]
>
> Deliberately creating identifiers that differ only by case
16 matches
Mail list logo