Date: Fri, 29 Aug 2014 12:11:27 +0200 From: John Marino <freebsd.contact@marino.st> To: Dmitry Marakasov <amdmi3@amdmi3.ru>, Tijl Coosemans <tijl@FreeBSD.org> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r366349 - head/archivers/rpm4 Message-ID: <540051CF.7000301@marino.st> In-Reply-To: <20140829100025.GQ55025@hades.panopticon> References: <201408272042.s7RKgFqF074882@svn.freebsd.org> <20140828101134.6f7b01ee@kalimero.tijl.coosemans.org> <20140828102214.GH34677@hades.panopticon> <20140828142822.73c5cef4@kalimero.tijl.coosemans.org> <20140829100025.GQ55025@hades.panopticon>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/29/2014 12:00, Dmitry Marakasov wrote: > * Tijl Coosemans (tijl@FreeBSD.org) wrote: > >> Does it test with a non-default prefix maybe? Because these directories >> really are in lang/python27/pkg-plist. It would at least have to be >> dirrmtry here, because other ports install files in those directories. > > Strange, poudriere doesn't complain on these any more (no, I haven't > used non-default prefix). So I've removed them. > > And yes, @dirrmtry should've been used here. Regarding directories > shared by multiple ports, I still don't have clear understanding: > on one hand, if a directory is managed by dependency, it shouldn't > appear in the port plist. On the other hand, if a port is installed > with non-default prefix, it should manage all dirs it uses on its > own. I probably would prefer the latter as it's more flexible and > less error prone (what if dependent ports plist change and directory > is no longer shared). if the directory is provided by a dependency 100% of the cases, then it shouldn't be in pkg-plist because it will try-fail 100% of the time. The non-standard prefix isn't an issue because all ports will have the same non-standard prefix. There's no difference. John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?540051CF.7000301>