Hi Jyri,
Thanks for the pointer to 2009/606.
I looked at the latest proposal sent this morning and noticed the file
layout is different than that used by postgres, one of the prime
examples people suggested I should follow for gcc.
Postgres puts most components under a single subdirectory:
/usr/postgres/8.3/bin
/usr/postgres/8.3/doc
/usr/postgres/8.3/etc
/usr/postgres/8.3/include
/usr/postgres/8.3/lib
/usr/postgres/8.3/man
/usr/postgres/8.3/share
while collectd proposes to put its subdirectories in multiple locations:
/usr/lib/collectd/4
/etc/collectd/4/conf.d
/var/collectd/4/rrd
/logs
/run
/usr/share/collectd/4
/usr/include/collectd/4
I had expected collectd to use something like the postgres layout but it
seems to have followed another variant. This leaves me confused as to
what standard I should follow for gcc.
Thanks,
George
Jyri Virkki wrote:
>
> On Nov 13, 2009, at 7:39 AM, Rainer Orth wrote:
>>> /usr/postgres/:
>>> 8.2/
>>> 8.3/
>>>
>>> I am happy to use whichever scheme is considered the correct precedent.
>>
>> Fine: in fact I think this is a job for ARC, to provide guidance here.
>
> This very question is a topic in 2009/606, also going on currently.
>
> It has not received a huge amount of discussion but the few opinions
> expressed are in favor of .../$COMPONENT/$VERSION/* directory hierarchy
> where applicable. That is also the more common layout among existing
> set of precedents, although there is a little bit of every variant in
> current Solaris.
