Date: Mon, 5 Jun 2017 02:54:52 +1000 From: Kubilay Kocak <koobs@FreeBSD.org> To: Pete Wright <pete@nomadlogic.org>, freebsd-ports@freebsd.org Cc: Thierry Thomas <thierry@FreeBSD.org> Subject: Re: py-enchant and wxPython Dependency Message-ID: <b2dbb572-1545-b20d-3b16-ae0f5067f87e@FreeBSD.org> In-Reply-To: <6cf0c9f7-133f-ec0b-3c46-8f3f9d9cba64@nomadlogic.org> References: <6cf0c9f7-133f-ec0b-3c46-8f3f9d9cba64@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/5/17 2:50 AM, Pete Wright wrote: > Hi there, > > I have a webapp that is making use of textproc/py-enchant for > spellchecking in some input forms we use. when i install py-enchant via > pip it only requires some libraries that ship with textproc/enchant. > yet when i install the py27-enchant pkg it looks like i have to slup in > about 1GB of deps - including lots of X libraries (libGL for example). > This seems to be related to having "USE_WX" flag set in the > textproc/py-enchant Makefile. > > Since my use-case is for a python webapp I have no need for wxPython and > it's dependency tree. Is there an easy way to re-build this port w/o > the wxPython dependency? I can confirm the py-enchant works fine > without wxPython when it is installed via pip inside a python venv. My > understanding is that the USE_* flags are not really meant to be > user-settable. > > Cheers, > > -pete > Hi Pete, If WX is optional (for enchant) then it should be made an OPTION to at least allow ports users to disable the dependency and its consequent features, and if you're a package user, the ability to create a custom package. This should take place as a request in Bugzilla (with rationale, etc) with a summary like: textproc/py-enchant: Make WX OPTION'al CC'ing port maintainer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b2dbb572-1545-b20d-3b16-ae0f5067f87e>