Hi Roland, On Fri, Feb 25, 2022 at 04:47:25PM +0100, Roland Rosenfeld wrote: > As an alternative I could package every module with dependencies as a > separate package, but I fear that this is overhead for the Debian > archive.
This seems to me to be the best solution long term TBH. lbdb isn't very useful without its plugins and if none of the plugin dependencies are installed by default for fear of bloat that makes it kind of annoying to use. Just think of what happens if a module changes which libraries it needs, as has already happened with the ldap module IIRC, the user has to keep up with that and implement it on their systems after the intial installation. That just not what I'd expect from a distribution package. Given how small most of these scripts are I don't really see the problem with having one package per module? In our wonderful distribution it just so happens that the smallest possible unit is a package so if we have to make one per module to make installtion more modular so be it :) --Daniel
signature.asc
Description: PGP signature
