Date: 17 Mar 2010 18:49:36 -0000 From: tmseck-lists@netcologne.de (Thomas-Martin Seck) To: freebsd-ports@freebsd.org Subject: Re: correct location for third party /var files Message-ID: <20100317184936.2310.qmail@wcfields.tmseck.homedns.org> In-Reply-To: <20100316183304.GF71601@hades.panopticon>
next in thread | previous in thread | raw e-mail | index | archive | help
* Dmitry Marakasov <amdmi3@amdmi3.ru> [gmane.os.freebsd.devel.ports]:
> * Eitan Adler (eitanadlerlist@gmail.com) wrote:
>
>> Are third party tools supposed to use /usr/local/var or /var ?
>
> /var, absolutely. Everything that uses /usr/local/var or, even worse,
> /usr/local/${PORTNAME} should be fixed.
I beg to differ, especially your absolute posturing, but take this as
the opinion of an aging fart.
When I started maintaining ports in 2004, the (or at least my) goal was
to avoid absolute paths in pkg-plist like the plague, that is why I do
not bother to use something /var/cache/squid or /var/log/squid instead
of PREFIX/squid/{logs,cache}. There is IMHO nothing wrong with storing
variable data in $PREFIX/portname/ as long as this is sensibly done.
$PREFIX/portname/var or $PREFIX/var/portname on the other hand is
usually just a sign of sloppy porting and should be fixed.
Trying to separate static and variable data and scattering said data
across filesystems just for the sake of it or for arcane aesthetic
reasons is - IMO - not really helpful for the user. The most important
point is that you should never deviate to much from the directory layout
that the software authors have in mind: users might have a hard time
finding out where a certain directory that is mentioned in the
documentation is actually located when the software is installed via
FreeBSD ports (my current case in point: mail/sympa5).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100317184936.2310.qmail>