> Deliver collectd 4.8.x into OpenSolaris
I have one issue from the pre-review of this case which seems worth
discussing in the ARC forum, namely the versioned directory layout.
There are many components in Solaris already with versioned file
layouts but AFAIK there is no consensus on the details. It would be
useful to have a precedent-setting case on that topic to avoid the
differing solutions from project to project.
Existing precedents vary. A few examples:
Most popular pattern is /usr/$COMPONENT/$VERSION/...
/usr/php/$version/*
/usr/mysql/$version/*
/usr/ruby/$version/*
/usr/lighttpd/$version/*
Some use /usr/$COMPONENT$VERSION/...
/usr/tomcat6/*
And some have both.. (historical reasons in both cases, IIRC)
/usr/apache2/$version/*
/usr/perl5/$version/*
As currently specified, this case (collectd) is proposing the second
variant, /usr/$COMPONENT$VERSION/ so /usr/collectd4/*
If we settle on the first variant, it should be /usr/collectd/4/*
As noted in s.2.2, collectd upstream considers their releases within
a major release family to be compatible, so only different major
releases need to coexist.
Other projects, such as apache httpd, are compatible only within minor
release family thus they specify major.minor as the $VERSION in
/usr/$COMPONENT/$VERSION/
At the other extreme is perl, which is using major.minor.micro as the
$VERSION (which seems excessive, but perhaps it was needed)
% ls -l /usr/perl5
total 16
drwxr-xr-x 5 root bin 512 Jun 18 2007 5.6.1
drwxr-xr-x 3 root bin 512 Jun 18 2007 5.8.3
drwxr-xr-x 5 root bin 512 Jun 18 2007 5.8.4
--
Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
