Hi!
On Wed, 2026-11-18 at 10:45:02 +0100, Enrico Zini wrote:
> On Tue, Nov 17, 2026 at 12:27:34AM +0100, Andrea Pappacoda wrote:
> > This is because the yuzu package needs to ship with a custom time zone
> > database format into the binary, and it is generated from the tzdata package
> > while building.
> >
> > Such scenario is still not ideal, but can be easily dealt with through a
> > binNMU. Having a source package ship its own database instead is way more
> > problematic in my opinion.
For the binNMU to be reasonable to handle, the embedding package should
then set the Static-Built-Using field, so that we do not need to track
affected packages by hand.
> I had a quick look. Would it in theory be possible to, say, ship tzdb2nx
> in /usr/lib, and build it on the user's system?
>
> This looks to me like a case for a tzdata dpkg trigger
In this particular case this might make sense, but in other cases, the
original data might not commonly be installed (dragging now this extra
dependency), it might be too large (which then would be doubled on disk),
or might take too long to transform, etc. In such cases a build time
transformation + Static-Built-Using + binNMUs might be a better
trade-off?
I also think it might be worth perhaps stating a gradient of preferred
solution stages towards a goal of full avoidance of database embedding.
Because not all projects (or maintainers) will be in a position to
migrate easily, and moving a step in the correct direction would be
better than blocking on trying to come up with the ideal end result.
Something like:
* Switch the code to use the canonical database.
→ Modify the code as needed.
* Code accesses the embedded database in an alternate location
on disk, and it's cumbersome to change the code.
→ Create compat symlinks and depend on database package.
* Project embeds the database in the executable/library.
→ Build depend on database package, and declare Static-Built-Using.
* Project converts canonical database to a custom format.
→ Depend on database and convert during install via triggers, or
→ Build depend on database package, convert at build time, and
declare Static-Built-Using.
(I'm probably missing other cases here, but I hope the idea comes
across.)
Thanks,
Guillem