Re: Vcs-* and shared repos

2016-06-28 Thread Johannes Schauer
Hi, Quoting Iustin Pop (2016-05-28 00:53:18) > If we go that way, they we should make it abstract: introduce Vcs-Path > and Vcs-Layout. Both of these are completely independent of the software > that hosts the code. this would also make it possible to have spaces in the path name without having

Re: Vcs-* and shared repos

2016-06-26 Thread Joachim Breitner
Hi, Am Freitag, den 24.06.2016, 15:38 +0100 schrieb Jonathan Dowland: > On Fri, Jun 24, 2016 at 03:02:57PM +0100, Joachim Breitner wrote: > > I never really understood why there is a games team; assuming that > > technically, almost every game is an island. (Ok, legal issues might be > >

Re: Vcs-* and shared repos

2016-06-24 Thread Jonathan Dowland
On Fri, Jun 24, 2016 at 03:02:57PM +0100, Joachim Breitner wrote: > I never really understood why there is a games team; assuming that > technically, almost every game is an island. (Ok, legal issues might be > similar). This is a very different situation than programming library > packaging. > >

Re: Vcs-* and shared repos

2016-06-24 Thread Jonas Smedegaard
Quoting Joachim Breitner (2016-06-24 16:02:57) > I never really understood why there is a games team; assuming that > technically, almost every game is an island. (Ok, legal issues might > be similar). This is a very different situation than programming > library packaging. Because not all

Re: Vcs-* and shared repos

2016-06-24 Thread Joachim Breitner
Hi, Am Freitag, den 24.06.2016, 09:17 +0100 schrieb Jonathan Dowland: > On Tue, May 24, 2016 at 11:24:43PM +0200, Iustin Pop wrote: > > The Debian Haskell team has migrated a while back from per-package > > repositories to a single repository which contains the packaging (only > > debian/) for

Re: Vcs-* and shared repos

2016-06-24 Thread Jonathan Dowland
On Tue, May 24, 2016 at 11:24:43PM +0200, Iustin Pop wrote: > The Debian Haskell team has migrated a while back from per-package > repositories to a single repository which contains the packaging (only > debian/) for the vast majority of packages >

Re: Vcs-* and shared repos

2016-06-23 Thread Jonas Smedegaard
Quoting Lars Wirzenius (2016-05-26 08:08:35) > On Wed, May 25, 2016 at 10:09:47PM +0200, Stefano Zacchiroli wrote: >> By also considering the fact that the "-d DIR" solution does not >> prevent to add a "-l" in the future, I think minimality wins here >> (hence my "Yay" to your proposal in

Re: Vcs-* and shared repos

2016-05-27 Thread Iustin Pop
On 2016-05-27 18:56:21, Tiago Ilieve wrote: > Iustin, > > On 27 May 2016 at 18:34, Iustin Pop wrote: > > That is a good point indeed. I'll think about it, but unless I find a > > much nicer solution I'll go ahead with the current one. > > > > At the moment I'm waiting to have

Re: Vcs-* and shared repos

2016-05-27 Thread Tiago Ilieve
Iustin, On 27 May 2016 at 18:34, Iustin Pop wrote: > That is a good point indeed. I'll think about it, but unless I find a > much nicer solution I'll go ahead with the current one. > > At the moment I'm waiting to have some free time to look at the vcswatch > and debcheckout

Re: Vcs-* and shared repos

2016-05-27 Thread Iustin Pop
On 2016-05-27 03:01:29, Tiago Ilieve wrote: > Hi Stefano, > > On 25 May 2016 at 17:09, Stefano Zacchiroli wrote: > > I'm convinced we will need at some point to document VCS packaging > > layouts in a way that allow tools to use that information > > programmatically. But right

Re: Vcs-* and shared repos

2016-05-27 Thread Tiago Ilieve
Hi Stefano, On 25 May 2016 at 17:09, Stefano Zacchiroli wrote: > I'm convinced we will need at some point to document VCS packaging > layouts in a way that allow tools to use that information > programmatically. But right now that information will not be actionable, > whereas

Re: Vcs-* and shared repos

2016-05-26 Thread Lars Wirzenius
On Wed, May 25, 2016 at 10:09:47PM +0200, Stefano Zacchiroli wrote: > By also considering the fact that the "-d DIR" solution does not prevent > to add a "-l" in the future, I think minimality wins here (hence my > "Yay" to your proposal in separate mail). YMMV. My only concern here is the

Re: Vcs-* and shared repos

2016-05-25 Thread Stefano Zacchiroli
On Wed, May 25, 2016 at 09:19:34PM +0200, Iustin Pop wrote: > And regarding layout: vcswatch already has code to try both > `/debian/changelog' and `/changelog' and use either of them. Having an > explicit layout (-l standard vs. -l native) would make this more > explicit rather than relying on

Re: Vcs-* and shared repos

2016-05-25 Thread Stefano Zacchiroli
On Wed, May 25, 2016 at 09:25:41PM +0200, Iustin Pop wrote: > 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

Re: Vcs-* and shared repos

2016-05-25 Thread Iustin Pop
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

Re: Vcs-* and shared repos

2016-05-25 Thread Iustin Pop
On 2016-05-25 09:34:43, Raphael Hertzog wrote: > My vote goes for changing nothing. IMO the extra convenience does not > outweigh the costs of having to support all the specific layouts in all > our infrastructure that wants to interact with the packaging git > repositories. I'm not sure this is

Re: Vcs-* and shared repos

2016-05-25 Thread Iustin Pop
On 2016-05-25 18:00:55, Joachim Breitner wrote: > Hi, > > Am Mittwoch, den 25.05.2016, 09:34 +0200 schrieb Raphael Hertzog: > > I fear that adding such expressivity is encouraging bad practice. While > > I can understand that a single repository can be convenient and easier > > to manage than

Re: Vcs-* and shared repos

2016-05-25 Thread Joachim Breitner
Hi, Am Mittwoch, den 25.05.2016, 09:34 +0200 schrieb Raphael Hertzog: > I fear that adding such expressivity is encouraging bad practice. While > I can understand that a single repository can be convenient and easier > to manage than proper "mr" usage, it also feels wrong on many levels: > - you

Re: Vcs-* and shared repos

2016-05-25 Thread Raphael Hertzog
Hi, On Wed, 25 May 2016, Stefano Zacchiroli wrote: > On Tue, May 24, 2016 at 11:24:43PM +0200, Iustin Pop wrote: > > A potential syntax for the Vcs-* fields would be: > > > > Vcs-Git: https://anonscm.debian.org/git/pkg-haskell/DHG_packages.git/ p/ghc > > I think something like this, or with the

Re: Vcs-* and shared repos

2016-05-25 Thread Joachim Breitner
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

Re: Vcs-* and shared repos

2016-05-25 Thread Geert Stappers
On Wed, May 25, 2016 at 08:25:09AM +0200, Stefano Zacchiroli wrote: > On Tue, May 24, 2016 at 11:24:43PM +0200, Iustin Pop wrote: > > A potential syntax for the Vcs-* fields would be: > > > > Vcs-Git: https://anonscm.debian.org/git/pkg-haskell/DHG_packages.git/ p/ghc > > I think something like

Re: Vcs-* and shared repos

2016-05-25 Thread Stefano Zacchiroli
On Tue, May 24, 2016 at 11:24:43PM +0200, Iustin Pop wrote: > A potential syntax for the Vcs-* fields would be: > > Vcs-Git: https://anonscm.debian.org/git/pkg-haskell/DHG_packages.git/ p/ghc I think something like this, or with the equivalent expressivity, would be useful and welcome, yes. I

Vcs-* and shared repos

2016-05-24 Thread Iustin Pop
Hi all, The Debian Haskell team has migrated a while back from per-package repositories to a single repository which contains the packaging (only debian/) for the vast majority of packages (https://anonscm.debian.org/cgit/pkg-haskell/DHG_packages.git/). This makes sense for us since the packaging