From owner-svn-ports-all@FreeBSD.ORG Sat Mar 28 04:40:11 2015 Return-Path: Delivered-To: svn-ports-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DB543F5B; Sat, 28 Mar 2015 04:40:10 +0000 (UTC) Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9F332C07; Sat, 28 Mar 2015 04:40:10 +0000 (UTC) Received: by padcy3 with SMTP id cy3so113983327pad.3; Fri, 27 Mar 2015 21:40:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:reply-to:subject:references:to:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=OWzPGfxMXKlf50R1cG9YtrwBYEIh1jOcDhCNyWamWT4=; b=d99qJNJtkX04LEaP1NVr+5WHQsH/V+9fwA5cy9+QdzySJB+4BwiNNY8NOPfCoOsvzK 3mpVn2Lo5beParQNGH4scm5Ag2zw8A7OFzRA7gWPbQkN5GaQAlsJgm/ElNbCyWDUelf9 bUl8/gSpGqgr244MjaUO2VeckDjD35BKtFrB5wh9wCekYJ63cNxUJnvMkUxxaSPD1rhd tNm1EJhP7Zlkq5BO+6mMs7YAs6Y33Dnt8GossqNpJ1uWILPWpukI5XGGEXWP5Cggh4op vno2NR4tbteJyRC7MW6TD1VwFqYpGVM6Cr8BuWWIqpPxSSOI9XXW9V4cuPYymWI1X/Tv 1Sew== X-Received: by 10.70.138.42 with SMTP id qn10mr40474918pdb.157.1427517610169; Fri, 27 Mar 2015 21:40:10 -0700 (PDT) Received: from [192.168.1.104] (ppp59-167-128-11.static.internode.on.net. [59.167.128.11]) by mx.google.com with ESMTPSA id yy2sm3689053pbb.6.2015.03.27.21.40.06 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Mar 2015 21:40:09 -0700 (PDT) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: svn commit: r382357 - in head/archivers: . py-python-snappy references: <201503262336.t2QNa3jg062494@svn.freebsd.org> <580752A5-F273-478B-8ABB-55883B2F32CC@FreeBSD.org> To: Dmitry Sivachenko , Antoine Brodin x-enigmail-draft-status: N1110 From: Kubilay Kocak message-id: <5516309C.20006@FreeBSD.org> Date: Sat, 28 Mar 2015 15:39:56 +1100 user-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Thunderbird/37.0 mime-version: 1.0 in-reply-to: <580752A5-F273-478B-8ABB-55883B2F32CC@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: "svn-ports-head@freebsd.org" , "svn-ports-all@freebsd.org" , python@FreeBSD.org, "ports-committers@freebsd.org" X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Mar 2015 04:40:11 -0000 On 28/03/2015 7:03 AM, Dmitry Sivachenko wrote: > >> On 27 марта 2015 г., at 12:52, Antoine Brodin >> wrote: >> >> On Fri, Mar 27, 2015 at 10:49 AM, Dmitry Sivachenko >> wrote: >>> >>>> On 27 марта 2015 г., at 2:36, Antoine Brodin >>>> wrote: >>>> >>>> Author: antoine Date: Thu Mar 26 23:36:02 2015 New Revision: >>>> 382357 URL: https://svnweb.freebsd.org/changeset/ports/382357 >>>> QAT: https://qat.redports.org/buildarchive/r382357/ >>>> >>>> Log: New port: archivers/py-python-snappy >>> >>> >>> Isn't this "python" in the middle excessive? Why not just >>> py-snappy? >> >> Upstream decided to name it python-snappy. When you use pip, you >> "pip install python-snappy" etc. >> > > > Yes, but you also added "py-" prefix, so with it "python-" became > excessive. Either py-snappy or python-snappy, but since "py-" is a > standard for FreeBSD ports, "python-" should be removed IMHO. > > The current target state (from Python@'s point of view) is: * Match upstream PyPi name, AND * py- prefix Unless there is a VERY compelling case *not* to do so. Exceptions to this *may* be pure CLI utility or "end-user" products, such as: sysutils/bsdploy devel/buildbot Even the above examples may not ultimately last as prefix-less ports in the tree longer term. There have been packaging naming conflicts in the past (some that still exist) due to the lack of a clear and consistent convention. One example is: twitter and python-twitter There are numerous others, and will continue to be in the future as upstreams control the names of their projects and packages. Kubilay