Creating a non-standard generic directory under /usr/lib breaks namespace.
Imaging a software project called exec that uses /usr/lib/exec for some
stuff - collisions may occure. You see breaking standards cause problems - at
least on systems that abide to standards. If each software developer
On Mon, 2005-05-30 at 07:20 +0530, Not Zed wrote:
On Sun, 2005-05-29 at 17:27 +0200, Christian Krause wrote:
Hi Rodney,
On 5/24/05, Rodney Dawes [EMAIL PROTECTED] wrote:
From the FHS:
Applications may use a single subdirectory under /usr/lib. If an
application uses a
Hi Rodney,
On 5/24/05, Rodney Dawes [EMAIL PROTECTED] wrote:
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
On Sun, 2005-05-29 at 17:27 +0200, Christian Krause wrote:
Hi Rodney,
On 5/24/05, Rodney Dawes [EMAIL PROTECTED] wrote:
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
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
Hello JP,
When installing evolution-data-server 1.2.x on a system which has a
FHS [1] compliant directory structure the evolution-data-server-1.2
binary is copied to a wrong place so that the evolution doesn't find
it. This results in a not-working evolution.
Why would this cause
On Sun, 2005-05-22 at 19:35 +0200, Christian Krause wrote:
Hello JP,
When installing evolution-data-server 1.2.x on a system which has a
FHS [1] compliant directory structure the evolution-data-server-1.2
binary is copied to a wrong place so that the evolution doesn't find
it. This
Hi,
When installing evolution-data-server 1.2.x on a system which has a
FHS [1] compliant directory structure the evolution-data-server-1.2
binary is copied to a wrong place so that the evolution doesn't find
it. This results in a not-working evolution.
The problem occurs, because in the FHS
