dpid doesn't work if configured with "--program-suffix=-new"
Hello, for the time being I'd like to install the current dillo version, next to the old existing one. So I configured with "--program-suffix=-new". Browsing works fine, but plugins (including bm or file) can't be started, as the binary is called "dpid-new" but dillo tries to start "dpid". It probaly wouldn't work anyway as $HOME/.dillo is hardcoded and there's no way to give a separate configuration directory (and sharing .dillo between different version is probably not a good idea). But it would be cleaner not to support "--program-suffix". Detlef
Detlef Vollmann wrote:
for the time being I'd like to install the current dillo version, next to the old existing one. So I configured with "--program-suffix=-new". Browsing works fine, but plugins (including bm or file) can't be started, as the binary is called "dpid-new" but dillo tries to start "dpid".
It probaly wouldn't work anyway as $HOME/.dillo is hardcoded and there's no way to give a separate configuration directory (and sharing .dillo between different version is probably not a good idea).
What about starting Dillo with: HOME=~/dillo-new dillo Then there's a script in the source code root directory called install-dpi-local. Running (from the Dillo source code dir): mkdir ~/dillo-new HOME=~/dillo-new ./install-dpi-local should install dpid and plug-ins to the ~/dillo-new/.dillo/dpi directory where dillo will find them when started in its own home. Alternatively you could manually make symlinks (if supported by your file system) in ~/dillo-new/.dillo/dpi to the "-new" binaries at their installed locations.
participants (2)
-
Detlef Vollmann
-
Kevin Koster