Hi, On Sat, Jul 1, 2023, 03:29 Dr. A. Krebs <i...@axel-krebs.de> wrote:
> Hi Guillermo: > > Thank you for information. > > Is a new library mandatory for a sw-package? > Nice-to-have or _really_ necessary? > The difference is irrelevant unless you compile your own version, as all official packages should ship (ideally) the same capabilities. In any case, sometimes there are security/performance changes in libraries that can't be avoided, and libraries are regularly deprecated in newer OS, so any dependent project must move along. Would enjoy to keep existing and proven sw as long as possible. > I guess, many other people might think similarly? > If you don't want to use an universal package, you have to use the darktable version shipped and compatible with your OS. You can't have both "existing and proven" and "latest and shiny" under the same metaphorical "library roof" (.deb use system libraries). The only way out of that is to use a flatpak/snap/appimage package, which avoid that conflict by shipping their own libraries, independent and isolated from the OS. :-) Thank all programmers for this wonderful piece of sw (-: > Axel > Best regards, Guillermo ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
