Re: [Evolution-hackers] installing evolution-data-server fails on a FHS compliant system

[Rodney Dawes <dobey novell com>]

Oh. Right. I thought libtoolize would fix it. We had the same problem
when packaging evolution for SUSE 9.3. What you need to do is not
specify libexecdir as $libdir. You need to set it as
$prefix/lib/something-else. The bug is still outside of evolution
though. This is because evolution has $libdir/evolution-$BASE_VERSION
for plug-ins and the like. Strictly speaking, you probably shouldn't
be installing executable binaries into $libdir directly anyway.

>From the FHS:

Applications may use a single subdirectory under /usr/lib. If an
application uses a subdirectory, all architecture-dependent data
exclusively used by the application must be placed within that
subdirectory.

This means that to be FHS-compliant, you need to specify the
evolution-$BASE_VERSION subfolder to $libdir for the --libexecdir
argument to configure. This is what we do in SUSE for
evolution-data-server.

-- dobey

On Tue, 2005-05-24 at 09:37 +0200, Frederic Crozat wrote: 
> This is not a problem with libtool and running libtoolize won't fix the
> problem. I hit the problem on Mandriva cooker when we switched to eds
> 2.2.2, for the exact same reason Christian explained, because evolution
> data server main process filename is the same as evolution library
> directory name (evolution-data-server-1.2), so when libtool installs the
> server executable, it find a directory with target name and will drop
> executable it it, without renaming it. The only way to fix this was to
> change .server.in.in to point to the new executable location.
> 
> But I've just realized changing executable filename will change process
> name and will break evolution --force-shutdown (which is broken ATM
> because it is still trying to kill evolution-data-server-1.0, as I
> realized 30s ago while checking code..).