From owner-freebsd-ports@freebsd.org Thu Oct 26 12:00:50 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85BFEE478AB for ; Thu, 26 Oct 2017 12:00:50 +0000 (UTC) (envelope-from rodrigo@osorio.me) Received: from smtp.osorio.me (smtp.osorio.me [5.196.94.126]) by mx1.freebsd.org (Postfix) with ESMTP id 5485C77905 for ; Thu, 26 Oct 2017 12:00:49 +0000 (UTC) (envelope-from rodrigo@osorio.me) Received: from [172.16.33.187] (unknown [213.174.108.235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.osorio.me (Postfix) with ESMTPSA id 16C623A81B for ; Thu, 26 Oct 2017 12:00:48 +0000 (UTC) Subject: Re: Files conflicts in ports To: freebsd-ports@freebsd.org References: <4b8e99ea-a9d9-c065-13a6-d54142cb2556@tuxfamily.org> <649b431c-3eba-c1ed-fa70-68a6c19850db@FreeBSD.org> From: Rodrigo Osorio Message-ID: Date: Thu, 26 Oct 2017 14:00:47 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <649b431c-3eba-c1ed-fa70-68a6c19850db@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Oct 2017 12:00:50 -0000 On 10/26/17 13:45, Kubilay Kocak wrote: > On 10/26/17 3:58 PM, L.Bartoletti wrote: >> Hi Rodrigo, >> >> Thank you for this precious tool. >> >> One question, seeing one of my ports which have conflicts >> (devel/py-gtfslib >> http://pkgtool.osorio.me/conflicts/lbartoletti@tuxfamily.org.html). Is >> it or not good to install test files? > > They're all effectively upstream bugs: installing modules into shared > locations. 'tests' is a common enough module name that its one of the > most easily observed in practice. > > There's nothing intrinsically wrong with tests being installed, but they > should be under/within their package module directories. > > Most projects exclude them (from installation) with something like: > > packages = find_packages(exclude=[...]), > > Though doing the above for a project with this packaging 'bug' is not > really the correct solution. Maybe for a short term > files/patch-setup.py, but report it upstream > >> Regards. >> >> Loïc >> >> On 10.10.2017 20:52, Rodrigo Osorio wrote: >>> Dear port maintainers, >>> >>> It appears that a number of ports install files with the same names at >>> the same locations, >>> causing file conflicts and unexpected behaviors for users. >>> >>> To help solving this issue I ran a tool to list per maintainer the >>> conflicting ports with >>> the list of impacted files ; the list is updated every day at 4am UTC. >>> >>> http://pkgtool.osorio.me/conflicts/ >>> >>> I believe most of the conflicts are trivial and can be solved with a >>> proper declaration in the CONFLICTS variable. >>> So take a look at it and don't hesitate to come back to me if you have >>> questions. >>> >>> best regards, >>> >>> - rodrigo >>> > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" I agree with Kubilay, If tests aren't relevant for production use the can be skipped. The point here is many (if not all) py- packages install the same test files and this is wrong. - rodrigo