Date: Wed, 24 May 2017 13:24:19 +1000 From: Kubilay Kocak <koobs@FreeBSD.org> To: Andriy Gapon <avg@FreeBSD.org>, sunpoet@FreeBSD.org, freebsd-ports@FreeBSD.org, Josh Paetzel <jpaetzel@FreeBSD.org> Cc: python@FreeBSD.org Subject: Re: py-backports.* conflict Message-ID: <0b8a6abb-7aa4-e3fb-adeb-30aa66743bc6@FreeBSD.org> In-Reply-To: <0fca8805-56b1-09d5-0237-ef76c0d3b47a@FreeBSD.org> References: <6ce74130-56f9-bed3-f5e5-c037c773cfc9@FreeBSD.org> <0fca8805-56b1-09d5-0237-ef76c0d3b47a@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/24/17 6:47 AM, Andriy Gapon wrote: > > [ping] > > On 18/05/2017 15:40, Andriy Gapon wrote: >> >> After the update of devel/py-backports.functools_lru_cache to 1.4 it started to >> conflict with devel/py-backports.shutil_get_terminal_size: >> >> py27-backports.functools_lru_cache-1.4 [FreeBSD] conflicts with >> py27-backports.shutil_get_terminal_size-1.0.0 [installed] on >> /usr/local/lib/python2.7/site-packages/backports/__init__.py >> >> It would be very inconvenient if only a single of py-backports.* ports could be >> installed at a time. >> >> Is it possible to fix the problem? >> > > These appear to be namespaced packages and all else being equal (bugs or other causes aside), the only way I can think of is to have a py-backports port, with subpackages for each py-backports.*, with py-backports owning the __init__.py (and other shared files, if any) and each sub-module (package) depending on py-backports for the shared bits. Having said that it could also be (at least partially) related to namespace package fixes that are in an unreleased version of shutil_get_terminal_size: https://github.com/chrippa/backports.shutil_get_terminal_size/pull/10 See Also: https://bbs.archlinux.org/viewtopic.php?id=226193 https://github.com/garbas/pypi2nix/issues/80
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0b8a6abb-7aa4-e3fb-adeb-30aa66743bc6>