Date: Thu, 25 Apr 2013 22:13:16 +0200 From: Florent Peterschmitt <florent@peterschmitt.fr> To: freebsd-ports@freebsd.org Subject: Re: Change design of py-* ruby-* ports Message-ID: <51798E5C.1030802@peterschmitt.fr> In-Reply-To: <2117909.R5VWH3vbkH@melon> References: <2117909.R5VWH3vbkH@melon>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
------enig2KFCNXNKBVOVJVOFMCFNP
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 25/04/2013 22:03, David Demelier wrote:
> Hello,
>=20
> Currently the ports tree has unified ports for python and ruby modules =
with=20
> origin like databases/py-sqlalchemy. When someone wants to bulk the por=
ts tree=20
> to create packages the databases/py-sqlalchemy will only be built again=
st the=20
> current python version set in Mk/bsd.python.mk (or overriden in make.co=
nf).
>=20
> This is a very bad design and we should fix that as soon as possible, w=
e are a=20
> lot of people and some portmgr folks included that is not the best way =
to=20
> manage python / ruby modules.
>=20
> Let say I want to install a package, unfortunately this one requires so=
me=20
> python modules that are only working for python 2.7 but me as a develop=
er I=20
> 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 respe=
ctive=20
> versions i.e py27-* and ruby19 (or 18?).
>=20
> Then we will need to copy all of these and set them to the newer versio=
n so=20
> py33 and ruby20.
>=20
> Also this will remove the breakage of OPTIONS, all of these ports needs=
the=20
> 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 th=
e best=20
> way to cover the both version and future bulk generation for users.
>=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.
But before (don't know when), it was like you say. py27-, py26, and
everything merged to py-
I was not as implied as now in FreeBSD project but it was surelly
motivated by something.
--=20
Florent Peterschmitt
+33 (0)6 64 33 97 92
florent@peterschmitt.fr
------------------------
O< ascii ribbon campaign
- stop html mail
- www.asciiribbon.org
------enig2KFCNXNKBVOVJVOFMCFNP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJReY5cAAoJEMtO2Sol0IImywgIAIbsWQg8LGskPRZT+b2Zinyr
HaLCVlREwn85bFy02KaDrB+5pHC+1vKYPWPS8SM+51hmn9gVsw+dQVA5RDKS11SI
D6nW0v4j83DRbFGRB7gc40ggZ2f7MGRkXkYmC2EPhvCXSCYzUvuTuK/5fj0weJ7Y
vWIUHVsh9uwkH2tY5/qvRVEJFTjPcMM/ia/4iRxwee0zCjzrs84RZzLEMLAFLh6D
hby4mUv/CdABuw+F8MeBC6ZsR/mBb/1U6njsRTtNMFYnQx/ejuXA+wjO6LG4QSG8
/tzIOEpGkfm83/tKOJ5w7sLPRT3EXrUc35lASVRNdSZ+nOeJkmYPCnEjyDgOo3c=
=+e+Y
-----END PGP SIGNATURE-----
------enig2KFCNXNKBVOVJVOFMCFNP--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51798E5C.1030802>