From owner-freebsd-ports@FreeBSD.ORG Thu Apr 25 20:21:43 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DF6F2FB9 for ; Thu, 25 Apr 2013 20:21:43 +0000 (UTC) (envelope-from demelier.david@gmail.com) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) by mx1.freebsd.org (Postfix) with ESMTP id 79CB71847 for ; Thu, 25 Apr 2013 20:21:43 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id m6so3882296wiv.9 for ; Thu, 25 Apr 2013 13:21:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding:content-type; bh=6LZqKAKr52naFBOnYFE6a1pWgzjVay70xCWmSMmT2Rg=; b=KjF3YfDmbUbmnFDe074qg1TlKqdEQeTDbeq9ZPzP1wQDijhRPe0/Ofb+jSxqx6jxhW F4mBSz09+aAhhDfHXmKVtzGIiS0buRxef4Q5gc6UmmUtdw4x3XaF9O0c1Ja2BF7Y7PhP DSYm94NbBx0L2p/GL6oqDc+Q9Yt//eA+SE9F6/ujy0kVeje18Sc+E27elxwBlXwnx5ah ifYGKJwQuCoIXWi+ydTcgF8gtPPkqXg/2sVdUkdtA61BIPUimJ0orZ5K57nmkIQ0lhuN 3+INKjeSEIpt12lwMRdqaE5HOLuNvfGnIl2BO0YpksWL22a29XMQiuH30rpfxtZU7/uh b9fg== X-Received: by 10.180.108.3 with SMTP id hg3mr62950wib.17.1366921302501; Thu, 25 Apr 2013 13:21:42 -0700 (PDT) Received: from melon.localnet (11.33.91.91.rev.sfr.net. [91.91.33.11]) by mx.google.com with ESMTPSA id j10sm40826049wie.1.2013.04.25.13.21.41 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 25 Apr 2013 13:21:41 -0700 (PDT) From: David Demelier To: freebsd-ports@freebsd.org, florent+FreeBSD-ports@peterschmitt.fr Subject: Re: Change design of py-* ruby-* ports Date: Thu, 25 Apr 2013 22:21:30 +0200 Message-ID: <170867095.QSZPI65LGS@melon> User-Agent: KMail/4.10.1 (FreeBSD/9.1-RELEASE-p1; KDE/4.10.1; amd64; ; ) In-Reply-To: <51798E5C.1030802@peterschmitt.fr> References: <2117909.R5VWH3vbkH@melon> <51798E5C.1030802@peterschmitt.fr> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2013 20:21:43 -0000 Le jeudi 25 avril 2013 22:13:16 Florent Peterschmitt a =E9crit : > On 25/04/2013 22:03, David Demelier wrote: > > Hello, > >=20 > > Currently the ports tree has unified ports for python and ruby modu= les > > with > > origin like databases/py-sqlalchemy. When someone wants to bulk the= ports > > tree to create packages the databases/py-sqlalchemy will only be bu= ilt > > against the current python version set in Mk/bsd.python.mk (or over= riden > > in make.conf). > >=20 > > This is a very bad design and we should fix that as soon as possibl= e, we > > are a lot of people and some portmgr folks included that is not the= best > > way to manage python / ruby modules. > >=20 > > Let say I want to install a package, unfortunately this one require= s some > > python modules that are only working for python 2.7 but me as a dev= eloper > > I > > want to develop with python 3, then we are stuck. > >=20 > > What we need to do now, is to move *all* py-* and ruby-* to their > > respective versions i.e py27-* and ruby19 (or 18?). > >=20 > > Then we will need to copy all of these and set them to the newer ve= rsion > > so > > py33 and ruby20. > >=20 > > Also this will remove the breakage of OPTIONS, all of these ports n= eeds > > the > > dirty hack of OPTIONSFILE because of the ${PKGNAMEPREFIX}. > >=20 > > This will blow out the ports tree by adding a lot of ports, but it'= s the > > best way to cover the both version and future bulk generation for u= sers. > >=20 > > Regards, >=20 > I agree with you. I thought about a PYTHON_VERSION=3D"27 33" variable= in > /etc/make.conf, generating each version of the module for each python= > version if the port is able to do it, but then you may build versions= of > module you don't need. >=20 This is something I think about too, but I'm not sure if it will be eas= y to=20 generate make package creating two ones for each version? And if a port requires a py- module but for a specific version, how is = it=20 possible to share PYTHON_VERSION=3D through dependencies? > But before (don't know when), it was like you say. py27-, py26, and > everything merged to py- >=20 > I was not as implied as now in FreeBSD project but it was surelly > motivated by something. --=20 David Demelier