Date: Fri, 14 Jan 2005 14:43:53 +0200 From: Adi Pircalabu <apircalabu@bitdefender.com> To: freebsd-ports@freebsd.org Subject: Re: HEADS UP: pkg-plist strict enforcement starting Message-ID: <20050114144353.1aad2014@apircalabu.dsd.ro> In-Reply-To: <1105704398.41e7b5ce7dc5e@buexe.b-5.de> References: <20050113062739.GA28658@xor.obsecurity.org> <Pine.LNX.4.44.0501131148520.25402-100000@pancho> <20050113180504.GA26064@xor.obsecurity.org> <20050114130404.250d6e26@apircalabu.dsd.ro> <20050114112918.GF69532@voodoo.oberon.net> <1105704398.41e7b5ce7dc5e@buexe.b-5.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 14 Jan 2005 13:06:38 +0100
Lupe Christoph <lupe@lupe-christoph.de> wrote:
> > It's better to use ~/.your_port directory in such cases.
>
> For system-wide defaults? Put them in /root/.foo.conf rather than
> /usr/local/etc/foo.conf?
For these specific cases, I do not think he meant installing anything
that should go system-wide in some user's home directory. Instead, I'm
thinking about setting port's dirs/files into ${PREFIX}/portname/
following a standard UNIX structure as in:
${PREFIX}/portname/bin/
${PREFIX}/portname/etc/
${PREFIX}/portname/lib/
${PREFIX}/portname/share/
${PREFIX}/portname/var/
and so on (where PREFIX will likely be /usr/local). All dirs/files
placed outside the above directory scheme will be completely deleted at
deinstall.
In my case, after port's deinstall, there will always be files left in
${PREFIX}/portname/. Is this a reason for tagging the port
BROKEN/IGNORE?
--
Adrian Pircalabu
Public KeyID = 0xF902393A
--
This message was scanned for spam and viruses by BitDefender.
For more information please visit http://www.bitdefender.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050114144353.1aad2014>