[Slackbuilds-users] udev rule clash

[KB_SBo]

On 5/2/26 03:55, Matteo Bernardini wrote:
> Il giorno sab 2 mag 2026 alle ore 12:22 Andrew Conway <nalumc at gmail.com 
> <mailto:nalumc at gmail.com>> ha scritto:
> 
>     I'm writing a slackbuild for FireCapture (https://
>     www.firecapture.de/ <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

Yes, I concur that plopping the udev rules into /usr/doc/... might be 
best now that INDI is in Slackware-Current.  While libindi has a bunch 
of driver and undev rules included, I will still be maintaining the 
additional 3rd party drivers and libraries. I might need to do something 
similar.

libindi-drivers
libindi-libraries

Looking at firecapture, there may be some camera library conflicts (ZWO 
ASI for example), so you may need to reference and itemize in your README.

https://drivers.indilib.org/cameras/

I was not aware of firecapture.  Looks nifty.


-Ed