The shared web layer forces a MySQL driver into LAPP #2
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Keel-Linux/keel-apache-php#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found while building LAPP on this layer, 2026-09-27.
Adminer depends on an alternation,
php-mysql | ... | php-pgsql, and apttakes the first name in the list. So
apache-phpinstallsphp-mysql, andevery child inherits it, including LAPP, whose database is PostgreSQL and
which has no use for a MySQL driver.
It is not fatal and it is not invisible: it is three packages of surface that
the stack does not use, in a layer whose whole purpose is to hold exactly what
both stacks need and nothing either one does not.
Closes when this layer names the driver it wants rather than letting the
alternation choose, and the LAPP chain no longer carries
php-mysql. Whetherthe shared layer should carry both drivers, so each stack finds the one it
needs, or neither, so each stack adds its own, is the decision to make and to
write down: the second keeps the layer honest, the first keeps the children
smaller by one package each.
Measured at the time: LAMP 520 packages, LAPP 515, and the difference between
a stack and its serverless variant is 13 and 10 packages, all of them the
database server's closure.