The way the /etc/init.d/mysql is written, it depends on the presence of /usr/portage and /var/db/pkg because it runs portageq during 'start'. In a squashfs based read-only install where the system has no need for /usr/portage and /var/db/pkg, this is a major pain to setup and start mysql. More so now that akonadi hard depends on mysql from KDE 4.13 and simple things like knotes does not work. So, is it possible to remove this dependency on portage tree and package database for mysql startup? Reproducible: Always
(In reply to devsk from comment #0) > The way the /etc/init.d/mysql is written, it depends on the presence of > /usr/portage and /var/db/pkg because it runs portageq during 'start'. > > In a squashfs based read-only install where the system has no need for > /usr/portage and /var/db/pkg, this is a major pain to setup and start mysql. > More so now that akonadi hard depends on mysql from KDE 4.13 and simple > things like knotes does not work. > > So, is it possible to remove this dependency on portage tree and package > database for mysql startup? > > Reproducible: Always The portageq command is only ever called when you forget to have initialized mysql/mariadb via emerge --config. It is used to construct an error message. I want to mark as WONTFIX, but willing to discuss a better option to produce a dynamic error message.
Looks like its only the error paths that need that dependency. I am willing to live with that. The startup failed because of something else (/var being ZFS). Sorry for wasting your time.
