Date: Fri, 05 Jul 2019 10:10:10 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 231392] print/py-psautohint: Update to 1.9.1 Message-ID: <bug-231392-21822-zZ3iCPVkL4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-231392-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-231392-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231392 --- Comment #14 from Ting-Wei Lan <lantw44@gmail.com> --- (In reply to Sunpoet Po-Chuan Hsieh from comment #12) psautohint isn't the only port requiring extra features from fonttools. I k= now it rarely changes, but it doesn't means it won't change. When it changes, it has to be propagated to all ports which copied these dependency lines from fonttools. It should be done in the same commit as the fonttools update to prevent possible breakage. If the person who updates fonttools doesn't know= he or she should update copies in other ports as well, these copies may eventu= ally become outdated. I don't like having duplicate code in a project, but it is OK for me to acc= ept your proposal if you agree to update all ports using extra features from fonttools whenever dependencies of options change. It is not an ideal solut= ion, but I can accept it as long as you don't ask me to keep them in sync by mys= elf and don't leave them outdated. I can add comments to the Makefile of fontto= ols, so you don't have to search the entire ports tree to find these copies. The ideal way to resolve the problem is probably adding a USES macro for fonttools, so we will have neither code copies nor many metaports. --=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-231392-21822-zZ3iCPVkL4>