This is not logical, and somewhat incorrect. The [ lensfun-data-v1 ] package needs no mention of the file, as the programme makes mention of it. In the worst-case scenario, the new version of lensfun already has the new camera/lens in its database, and any references to the same camera/lens in any extraneous files are ignored.
What system-wide updates do is that only one user has to run the update, (and we assume that that one user is a sysadmin who knows what they are doing). With local updates, all users have to run the update, creating multiple copies of the same file. Turning Debian into Windows is not a good idea. 😄😉 The only time a local update is advised, is when creating a custom entry for some non-standard camera/lens combination, such as a howe-made, Frankenstein, macro-lens. That is NOT something which one would necessarily want other users to have in their database. Sincerely, Karim Hosein Top Rock Photography 754.999.1652 On Sat, 5 Sep 2020 at 10:42, Timur Irikovich Davletshin < [email protected]> wrote: > Let's imagine new camera or lens family appears, this creates new file > in lensfun data structure. This file is orphaned since it is not > mentioned in lensfun-data-v1 package. During regular apt update this > will create mess. Turning Debian into Slackware is not a good idea 😄 > > Timur. > > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
