[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libexecdir/datadir used incorrectly

From: Eli Zaretskii
Subject: Re: libexecdir/datadir used incorrectly
Date: Wed, 09 Feb 2005 06:55:51 +0200

> From: "Alfred M. Szmidt" <address@hidden>
> Date: Tue, 08 Feb 2005 22:42:39 +0100
> Cc: address@hidden, address@hidden
>    + The definition of @samp{libexecdir} is the same for all packages, so you
>    + should install your data in a subdirectory thereof.  Most packages
>    + install their data under @file{$(libexecdir)/@var{package-name}/}.
> This is actually wrong (but only for libexecdir), most packages
> install under:
> if they install in a subdirectory in /libexec (emacs, and gcc are
> prime examples). MACHINE is the GNU machine tripple.

To claim that ``most packages'' do that, you need a better statistics
than 2 examples, even if they are ``prime''.  In standards.texi, I'd
prefer not to talk about what _most_ packages do, but about what
packages _should_ do.

(And while at that, please try not to change the
conventions/instructions too frequently, even if the current
conventions seem not 100% right.  One important aspect of coding
standards is that they stay relatively unchanged, especially where
installation instructions are concerned.  The recent changes made it
all but impossible to predict where a particular package will put its
data files and subprograms, since it depends on what version of the
standards the package maintainer succeeded to pick up.  That's BAD,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]