-----BEGIN PGP SIGNED MESSAGE-----
Tzafrir Cohen wrote:
>> (yet anyway)), live-helper works away solidly, but then crashes in
>> postinst when the database would ordinarily be created since mysql is
>> installed, but not running in the chroot.
> I don't think that debian-live is the only scenario where a package is
> installed in a chroot.
No, I'm sure it isn't, but maybe it's the non-running mysql that's the
>> Is there any accepted way around this? I have thought of special init
>> scripts and special packages, but I wanted to ask if there was a known
>> workaround for this problem first.
> What if mysql is already running on the main system?
It is / was. I think the issue was that the socket path was pointing to
the /var/run/ directory in the chroot where there was no running server.
> Anyway, any chance that application can work with an sqlite database?
Hmm, I don't know, I've never played with sqlite, but looking at it
briefly, I think that would cause more work since I'd have to do a lot
of testing on a new backend to ensure the application still worked
One workaround I wondered about was amending the postinst script to
check if it was a live-helper install, and if so to not call the
database configuration sections. I could then execute an init script
that performed either a dpkg-reconfigure on the packages or directly
called a script to import the SQL.
Does that sound credible, and if so is there a reliable way of detecting
that I'm in the live-helper build environment?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----