Re: [PATCH 2/7] Conffile database handling functions

2011-05-09 Thread sean finney
On Mon, May 09, 2011 at 12:36:28PM +0200, Raphael Hertzog wrote: > > [1] checking the multi-arch status of the package's previous version to > > determine the conffiledb path at appropriate points in the code, > > assuming that can be done. > > I have not looked into details but I don't se

Re: [PATCH 2/7] Conffile database handling functions

2011-05-09 Thread Raphael Hertzog
On Mon, 09 May 2011, sean finney wrote: > On Sun, May 08, 2011 at 09:05:20PM +0200, Raphael Hertzog wrote: > > The control files are installed as .foo except for Multi-Arch: same > > which are installed as :.foo. > > > > It's probably a good idea to reuse the same logic here. > > If a package mig

Re: [PATCH 2/7] Conffile database handling functions

2011-05-09 Thread sean finney
hiya, On Sun, May 08, 2011 at 09:05:20PM +0200, Raphael Hertzog wrote: > On Sun, 08 May 2011, sean finney wrote: > > I'd think that only one instance of arch:all could be installed, but I > > haven't read the details of how we're doing multi-arch so perhaps someone > > with better insights could c

Re: [PATCH 2/7] Conffile database handling functions

2011-05-08 Thread Raphael Hertzog
On Sun, 08 May 2011, sean finney wrote: > I'd think that only one instance of arch:all could be installed, but I > haven't read the details of how we're doing multi-arch so perhaps someone > with better insights could confirm/clarify? The control files are installed as .foo except for Multi-Arch:

Re: [PATCH 2/7] Conffile database handling functions

2011-05-08 Thread sean finney
On Fri, May 06, 2011 at 10:58:46AM -0500, Jonathan Nieder wrote: > > I think pkg:arch would suffice instead of pkg, right? > > Yes, probably. I'm not sure whether arch:all packages are currently > tied to a specific arch. I'd think that only one instance of arch:all could be installed, but I hav

Re: [PATCH 2/7] Conffile database handling functions

2011-05-06 Thread Jonathan Nieder
sean finney wrote: > I think pkg:arch would suffice instead of pkg, right? Yes, probably. I'm not sure whether arch:all packages are currently tied to a specific arch. > Yeah, I think previous versions of the patch series had "new", "old", > "tmp", "cur" or similarly named directories, and vari

Re: [PATCH 2/7] Conffile database handling functions

2011-05-06 Thread sean finney
On Fri, May 06, 2011 at 02:59:52AM -0500, Jonathan Nieder wrote: > Ah, memories. The main piece to revisit might be what sort of > identifier to use for in these modern days of multiarch. I also I think pkg:arch would suffice instead of pkg, right? > think there was some talk about atomic rena

[PATCH 2/7] Conffile database handling functions

2011-05-06 Thread Jonathan Nieder
From: Sean Finney Date: Mon, 14 Dec 2009 08:27:32 +0100 (Note: this information is largely duplicative of the doxygen documentation comments, found in conffiledb.c and conffiledb.h) The files conffiledb.{c,h} define a set of routines for adding and removing stored versions of "pristine" conffile

Re: [PATCH 2/7] Conffile database handling functions

2010-02-08 Thread sean finney
hi guillem, i'll try to answer these in order, here's the first to look over while i start looking over the next. On Sun, Feb 07, 2010 at 08:24:55PM +0100, Guillem Jover wrote: > On Mon, 2009-12-14 at 08:27:32 +0100, Sean Finney wrote: > > The layout pattern for the conffile database is: > > > >

Re: [PATCH 2/7] Conffile database handling functions

2010-02-07 Thread Guillem Jover
Hi Sean! On Mon, 2009-12-14 at 08:27:32 +0100, Sean Finney wrote: > The layout pattern for the conffile database is: > > /conffiles/// While the implementation resulting from this layout seems more elegant than the previous iteration, I still think that using the layout I described in the

[PATCH 2/7] Conffile database handling functions

2009-12-13 Thread Sean Finney
(Note: this information is largely duplicative of the doxygen documentation comments, found in conffiledb.c and conffiledb.h) The files conffiledb.{c,h} define a set of routines for adding and removing stored versions of "pristine" conffile versions as shipped in their respective packages. Such a