changing the install location of hal-system-power-pmu to libexec

Richard Hughes hughsient at gmail.com
Fri Feb 17 04:06:34 PST 2006


On Fri, 2006-02-17 at 11:38 +0000, Matthew Garrett wrote:
> On Thu, Feb 16, 2006 at 03:56:32PM -0800, Artem Kachitchkine wrote:
> > 
> > >to /usr/share/hal/scripts, as it's quite clearly not a script.
> > >
> > >In CVS, the hal-power-brightness-* scripts assume it's in the latter, so
> > >don't work for pmu at the moment. [1]
> > 
> > Why can't we just rename directory from an implementation attribute to 
> > something that answers the question "What's in this directory?" Because the 
> > answer "scripts" only sparks one's curiosity: "What kinda scripts? Can I 
> > put any script in it?" Calling it "method" or something is less ambiguous.
> 
> Just renaming it isn't an option unless it also moves out of /usr/share 
> - compiled C code has to go under /usr/lib (or libexec).

I've been playing with re-writing the hal-power-* scripts in python,
thus removing the problem (as python can do ioctls). Would this be
acceptable as a solution?

Richard.



More information about the hal mailing list