Date: Sun, 20 Dec 2015 10:45:39 +0200 From: Mykola Golub <trociny@FreeBSD.org> To: freebsd-python@freebsd.org Subject: porting PyECLib Message-ID: <20151220084538.GA2784@gmail.com>
next in thread | raw e-mail | index | archive | help
Hi, Newer versions of the openstack swift require PyECLib: https://bitbucket.org/kmgreen2/pyeclib So preparing an update for databases/py-swift I have created PyECLib port: https://people.freebsd.org/~trociny/patches/py-PyECLib.ports.1.diff I am not sure about some things though: 1) Portname: currently PyECLib, but may be it should be pyeclib or just eclib? 2) The package includes several C libraries: gf-complete, liberasurecode, jerasure, which are their own projects, so could be built as separate packages. Do you think it worth splitting it to several packages, providing the libraries as dependencies to PyECLib? I suppose it could be splitted later if other users for the libs are found. 3) May be you see other things I do wrong here? -- Mykola Golub
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151220084538.GA2784>