Small feature request for 0.5.9

[David Zeuthen]

Hi!

On Fri, 2007-03-30 at 11:22 +0200, Arnaud Quette wrote:
> I would really need an "addondir" variable in hal.pc to get to exact
> path to install the NUT addons...

I just clarified this in the spec with this commit

 http://gitweb.freedesktop.org/?p=hal.git;a=commitdiff;h=e7010183bf3a052f13bd735669cfc4b5e846bdab

and I uploaded a version with this change here

 http://people.freedesktop.org/~david/hal-spec/hal-spec.html#device-properties-info-callouts

The answer: to be portable, install your addon in $libdir/hal/scripts

(e.g. where $libdir typically is is /usr/lib or /usr/lib64)

> Something that would act like:
> pkg-config --silence-errors --variable=addondir hal
> => /usr/lib/hal/
> 
> The same goes for the fdi file. IMHO, this should point the thirdparty
> directory, since it's oriented toward external apps.

This should already be clarified in the spec in this section. 

 http://people.freedesktop.org/~david/hal-spec/hal-spec.html#id3065099

The answer here is: install your information fdi files (for matching
supported devices) in

 $datadir/hal/fdi/information/20thirdparty

and the policy files (for launching the addon) in

 $datadir/hal/fdi/policy/20thirdparty

You may combine both files into a single one; in that case put it in
'policy' rather than 'information'.

(e.g. where $datadir typically is is /usr/share)

Does that help?

> Since I'm currently finishing the NUT to HAL bridge, I'll need this to
> produce some final integration and packages.

Cool, I'd love to look at the code and give feedback on it. Do you have
a pointer?

    David