[gphoto-devel] [PATCH 0/2] remove deprecated keys from HAL

[Dan Nicholson]

On Tue, Mar 4, 2008 at 10:06 AM, Danny Kukawka <danny.kukawka at web.de> wrote:
> On Dienstag, 4. März 2008, Hubert Figuiere wrote:
>  > On Tue, 2008-03-04 at 12:42 -0500, David Zeuthen wrote:
>  > > On Tue, 2008-03-04 at 00:54 +0100, Danny Kukawka wrote:
>  > > > This really sucks. They had 12 months time to update their projects. If
>  > > > you have a project that relies on HAL you should be able to take every
>  > > > some months a look at the spec to see what changed.
>  > >
>  > > Also NetworkManager needs to be unbreaked
>  > >
>  > > http://gitweb.freedesktop.org/?p=hal.git;a=commitdiff;h=73a372961d6a25cad
>  > >5923350210bbed1621cdbb1
>  > >
>  > > At least this way we can track down the offending projects. But do
>  > > expect a lot more things to break.
>  >
>  > Maybe providing a clear mechanism to deprecate keys? Because with these
>  > changes you are clearly breaking the *ABI*.
>
>  There is IMO a clear mechanism. If keys get replaced and with this deprecated,
>  they get removed from the SPEC and added to the 'Deprecated Properties'
>  section of the HAL spec with the info which property/key replaced them and at
>  which date they get removed finally. And there is also the release news which
>  normaly contains info about the remove.

But how is that associated to a version? What if I want to run gphoto
trunk on hal-0.5.8.x? The libhal API says that's OK, but then it has
no idea about an "originating_device".

--
Dan