[Slackbuilds-users] udev rule clash
Matteo Bernardini
matteo.bernardini at gmail.com
Sat May 2 10:55:54 UTC 2026
Il giorno sab 2 mag 2026 alle ore 12:22 Andrew Conway <nalumc at gmail.com> ha
scritto:
> I'm writing a slackbuild for FireCapture (https://www.firecapture.de/).
> It ships with udev rules for various astronomical cameras but these udev
> rules already exist on my system from libindi packages, and are likely to
> for other astro minded folk too.
>
> My first thought is to exclude these udev rules in the FireCapture package
> unless the user has set an environment variable to explicitly say they want
> them included, and note that in the README.
>
> Is that OK? Is there a convention for how slackbuilds should handle such
> udev rules?
>
hi Andrew,
usually you can install them, if they don't overlap with something else...
in this case and considered also that libindi is part of Slackware since
this iteration of current (so it will be in the next stable release), IMHO,
you could let the SlackBuild install them and then, still in the
SlackBuild, move them away in the /usr/doc/firecapture-$VERSION directory,
adding a note in the README that one has to manually copy the udev rule for
his own hardware in the /etc/udev/rules.d directory.
Matteo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20260502/8fb2d7f7/attachment.htm>
More information about the SlackBuilds-users
mailing list