On Thu, 2014-08-14 at 09:56:55 +0200, Raphael Hertzog wrote:
> On Sat, 12 Jul 2014, Felix Berlakovich wrote:
> > I applied the patch from Vasily i. Redkin to version 1.17.10 (and moved
> > a redundant part into an own function). BTW his patch works great.  I
> > did this in preparation for a possible threeway merge improvement. Is
> > there still any interest in such a feature? Is there any reason why this
> > patch was never integrated?
> 
> Paul Wise pointed me at http://community.libelektra.org/wp/?p=145 and
> http://community.libelektra.org/wp/?p=153 which in turn brought
> me back to this email.

I noticed the initial blogs about elektra some time ago, and was
surprised (not in a positive way) that yet another time a GSoC had
been approved w/o any kind of previous interaction with a project it
supposedly required coordination with. Had pending sending myself a
mail to the gsoc list but had other stuff to do, and pretty much lost
the motivation after those blog posts… :/

> 4/ yes we are interested in the feature but dpkg is an important piece of
>    software and we must get it right from the start, so extra caution is
>    always a good idea

I think I've mentioned before, in any case I'm planning on getting
the conffiledb stuff ready hopefully before the freeze. Which is a
requirement for this bug being fixed.

> which then links to
> https://wiki.debian.org/Teams/Dpkg/Proposals/ConffileDatabase
> which contains the most recent attempt to bring this feature
> to Dpkg. Sean Finney was working on this but unfortunately
> he lost motivation due to lack of review by Guillem. Fortunately Guillem
> is much more responsive nowadays so you might have more luck
> to bring it to a mergeable state.

Err, that's not what happened… it got old pretty quick when it was
obvious that the reviews were being ignored, from both me an Jonathan,
and Jonathan said as much on the list after similar claims appeared
there…

Guillem


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to