[Nut-upsuser] Install problems (group permissions) with nut 2.7.2
rgroner at RTD.com
Tue Mar 10 12:38:51 UTC 2015
It's arbitrary to me what version I start from, I had just grabbed the latest 2.7.2 tar.
How do I get the version that you suggest I start from? git clone? Or do I just change the .tar file I have with what you linked (changes the 52-* file to 62-*)
> -----Original Message-----
> From: Charles Lepple [mailto:clepple at gmail.com]
> Sent: Monday, March 09, 2015 8:48 PM
> To: Rob Groner
> Cc: nut-upsuser List
> Subject: Re: [Nut-upsuser] Install problems (group permissions) with nut
> On Mar 9, 2015, at 12:00 PM, Rob Groner <rgroner at RTD.com> wrote:
> > 1) Autoreconf *must* be run, and not ./configure? I had thought that
> putting in my *.c and *.h files and making the makefile changes and then
> executing ./configure for the first time would be enough.
> Each tool serves a different purpose. autoreconf (and NUT's autogen.sh, by
> inclusion) generates the ./configure script. I think it typically runs it as well,
> but often you would re-run it with "--prefix=" or other arguments (such as "--
> with-drivers=usbhid-ups" to cut down on compilation time).
> It occurred to me that your driver will be introducing new USB VID:PID
> entries, so this is something else that autogen.sh does: it rebuilds the udev
> files that change permissions when the UPS gets plugged in.
> I mentioned pulling in a copy of autogen.sh earlier, and I'm not sure what
> other developer-only scripts are left out of the tarball. We really only heavily
> test two cases: building from Git, and building from a clean tarball. Small
> patches to the tarball are easy; structural changes like adding files are harder
> to guarantee that they will work.
> That, plus the fact that 2.7.2 still has the old prefix number on the udev files,
> means you might be better off starting from the latest Git version of NUT, or
> at least including the following patch:
> Charles Lepple
> clepple at gmail
More information about the Nut-upsuser