Hi! Markus, please reply to the list, we others are only seeing half of the discussion.
On Mon, Mar 31, 2014 at 2:01 PM, Paul Fertser <[email protected]> wrote: > On Mon, Mar 31, 2014 at 01:25:40PM +0200, Markus Mayer wrote: > >> Regarding udev rules, hm, do you think it'd be appropriate to use > >> "pkg-config --variable=udevdir udev" and if present to copy the rules > >> file to DESTDIR+prefix+(that path) during make install? Sounds a bit > >> too hacky. > > > > I would just hard code the path to either /etc/udev[...] or > > /usr/share/udev[...]. The packager can fix this easily. It's only > > important to have it in a standard udev dir. > > Why would the udev pc file contain that variable if the udev authors > thought everyone should hardcode /etc/udev path? > It doesn't matter if udev always uses the same dir because other systems do not use udev at all. Given that, I find it crazy to keep track, in OpenOCD, of which operating systems use udev and, if they do, where the rules file should reside, what user should own the devices, suitable permissions and so on. And duplicating that knowledge in all other software. Keeping track of such things is a job for the packager of the software for the respective operating system. Setting up the system (which may involve copying the udev rules) should probably be done in a post-install script of the package. BTW, do you probably know of any examples of well-known software that > copies udev rules during make install? > I don't think installing a tarball should mess with the system configuration, which is what udev rules are. Please do not get me wrong, but I'd really like to have a correct > long-term solution. > I think we already do. /Andreas
------------------------------------------------------------------------------
_______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
