Date: Sun, 03 Jan 2016 20:59:23 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 205852] Be nicer about multiple sqlalchemy ports Message-ID: <bug-205852-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205852 Bug ID: 205852 Summary: Be nicer about multiple sqlalchemy ports Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Some People Priority: --- Component: Ports Framework Assignee: portmgr@FreeBSD.org Reporter: mi@FreeBSD.org CC: freebsd-ports-bugs@FreeBSD.org, lwhsu@FreeBSD.org I'm porting something called MediaGoblin, which requires sqlalchemy above 0= .8 (it uses the new with_polimorph feature), but also sqlalchemy-migrate and alembic. Currently, sqlalchemy-0.8 is installed by databases/py-sqlalchemy-devel and creates package named sqlachlemy08 Those two list py-sqlalchemy>0.7 among dependencies, which translates into databases/py-sqlalchemy. I'm proposing a patch, which relaxes the DEPENDS-line to accept whatever sqlalchemy is already installed on the system: -RUN_DEPENDS=3D=20=20 ${PYTHON_PKGNAMEPREFIX}sqlalchemy>=3D0.7:${PORTSDIR}/databases/py-sqlalchem= y \ +RUN_DEPENDS=3D=20=20 ${PYTHON_PKGNAMEPREFIX}sqlalchemy*>=3D0.7:${PORTSDIR}/databases/py-sqlalche= my \ Although my patch addresses only the two ports mentioned (maintainer CC-ed)= , it is very likely, that most (if not all) of the other ports needing sqlalchemy could do the same thing -- which is why I'm calling portmgr's attention to = this ticket. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-205852-13>