Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Mar 2010 00:48:11 +0200
From:      Ion-Mihai Tetcu <itetcu@FreeBSD.org>
To:        tmseck-lists@netcologne.de (Thomas-Martin Seck)
Cc:        freebsd-ports@freebsd.org
Subject:   Re: correct location for third party /var files
Message-ID:  <20100318004811.57d0f060@it.buh.tecnik93.com>
In-Reply-To: <20100317184936.2310.qmail@wcfields.tmseck.homedns.org>
References:  <20100316183304.GF71601@hades.panopticon> <20100317184936.2310.qmail@wcfields.tmseck.homedns.org>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/GsFB6a.s1EH.34P5dW6+IWO
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On 17 Mar 2010 18:49:36 -0000
tmseck-lists@netcologne.de (Thomas-Martin Seck) wrote:

> * Dmitry Marakasov <amdmi3@amdmi3.ru> [gmane.os.freebsd.devel.ports]:
>=20
> > * Eitan Adler (eitanadlerlist@gmail.com) wrote:
> >=20
> >> Are third party tools supposed to use /usr/local/var or /var ?
> >=20
> > /var, absolutely. Everything that uses /usr/local/var or, even
> > worse, /usr/local/${PORTNAME} should be fixed.
>=20
> I beg to differ, especially your absolute posturing, but take this as
> the opinion of an aging fart.
>=20
> 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.
>=20
> 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).

Sorry to say, but you are very wrong.

There is nothing arcane about wanting to have about wanting to have
everything that's rw (as opposed to only r) on a separate file system.

Squid and sympa ports are wrong. So are a ton of www ports.

Just as an example, think of Nth jails which could nicely share via a
nullfs mount everything but the files that are either config or
variable from a "base" jail.

--=20
IOnut - Un^d^dregistered ;) FreeBSD "user"
  "Intellectual Property" is   nowhere near as valuable   as "Intellect"
FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B

--Sig_/GsFB6a.s1EH.34P5dW6+IWO
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (FreeBSD)

iEYEARECAAYFAkuhXDMACgkQJ7GIuiH/oeURHwCbB4RXAz+WWNG+N0PIWJPTVjXP
GsQAnjB+g34zNv5Nw0Xu1n6NEa5/B4Ee
=DIdy
-----END PGP SIGNATURE-----

--Sig_/GsFB6a.s1EH.34P5dW6+IWO--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100318004811.57d0f060>