Re: libexecdir/datadir used incorrectly

[Karl Berry]

      2. Maybe the GCS need to state more clearly that packages
         should not install data directly in $(datadir), but rather
         do so in a subdirectory, because the definition of
         $(datadir) is the same for all projects.     

I guess so.  The current text basically says you're supposed to install
pkg-specific data in datadir:

    @item datadir
    The directory for installing idiosyncratic read-only
    architecture-independent data files for this program.  

Which is why I came to the conclusion I did.  I'm happy to know that
this isn't right and datadir means what it always did.

Alfred, as far as I can see all your patch does is change "The default
definition" to "By default".  I don't see the point.

Alexandre or Alfred or anyone, can you suggest new wording that
concisely explains the real situation and what maintainers are supposed
to do?  Here's the full datarootdir/datadir description now ...

Thanks,
k

@item datarootdir
The root of the directory tree for read-only architecture-independent
data files.  This should normally be @file{/usr/local/share}, but
write it as @file{$(prefix)/share}.  @samp{datadir}'s default value is
based on this variable; so are @samp{infodir}, @samp{mandir}, and others.

@item datadir
The directory for installing idiosyncratic read-only
architecture-independent data files for this program.  This is usually
the same place as @samp{datarootdir}, but we use the two separate
variables so that you can move these idiosyncratic files without
altering the location for Info files, man pages, etc.

The default definition of @samp{datadir} should be
@file{$(datarootdir)}.  (If you are using Autoconf, write it as
@samp{@@datadir@@}.)