From mboxrd@z Thu Jan 1 00:00:00 1970 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> MIME-Version: 1.0 Date: Sun, 12 Sep 2010 10:57:13 -0600 From: EBo In-Reply-To: References: Message-ID: <24b6a153e443aa375714b80fe48294de@swcp.com> User-Agent: RoundCube Webmail/0.3.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] docfonts problem Topicbox-Message-UUID: 55638ce0-ead6-11e9-9d60-3106f5b1d025 As I said, I would ask Bigelow & Holmes for final clarification before releasing anything. I am not trying to dance around the license, but get clarification on what is OK. I have made it a habit of asking people her= e, and elsewhere, if there they would mind if I do something in a particular way. I have even caught flack for asking 9fans before "showing them the code", but it is exactly this kind of toe stepping that I like to avoid. = I could go through the dance steps of how portage can download multiple source trees to build stuff, but you have made it quite clear how you fee= l about it.=20 Now for the problem behind all this. I am basically required to use trof= f for formatting the iwp9 paper submissions. I have asked repeatedly for t= he a TeX macros, or the source for an acceptable macro.ms equivalents. All = of these requests have been greeted with silence because someone, and I woul= d have to guess who, is discouraging the use of TeX for these submissions.=20 Frankly troff has been a pain, and I do not use it for anything else, and will not except for necessary plan9 related documentation. Thanks for th= e work around BTW, but next time I rebuild plan9port it will be blown away unless I add these dance steps to the ebuilds. See the chicken ant the e= gg problem? As for Gentoo, I would have to go through a formal review before having them added to any repository AND the licensing field in portage ebuilds explicitly contain all the licenses of the software used to build the programs. So, gentoo would know right off -- I would not hide it. Also, there are ebuilds for proprietary closed-source programs in gentoo, thoug= h not many. On Sun, 12 Sep 2010 11:42:13 -0400, Russ Cox wrote: >>> do you have the fonts? >>> they do not come with plan9port, because the >>> postscript fonts cannot be redistributed except >>> with plan 9 itself. >> >> turns out no. =C2=A0Here is a sticky question (one I will likely have = to >> write >> Bigelow & Holmes for final clarification), but if I write a script >> (portage >> ebuild) which downloads and extracts the fonts into plan9port so all this >> works. =C2=A0Is this a violation of their license? =C2=A0I would not b= e >> redistributing it, but would this be considered a derivative work? >=20 > where would the script download them from? > whoever makes them available for download > separate from plan 9 is violating that license. > further, this kind of dancing on the edge of a knife > approach to software licensing is not typically > looked kindly upon by the distributions. i bet > gentoo would object if they found out. >=20 > honestly, i wouldn't play these games. >=20 > bigelow & holmes granted plan9port a license to > distribute plan 9's lucida bitmap fonts as long as > they were named something other than lucida > (that's why the directories are named luc instead > of lucida), and that same license explicitly excluded > plan 9's lucida sans postscript fonts. they were very > gracious about licensing even the bitmap fonts when > there was little benefit to them other than good will. > instead of violating the spirit and possibly the letter > of both licenses, i would suggest that you use the > postscript fonts that i substituted in their place, namely > luxi sans, also by bigelow & holmes. the ms macros > that ship with plan9port use them if you start your > document with >=20 > .FP luxisans >=20 > they have equally good unicode coverage and a > similar look to lucida sans. >=20 > if you do write such a script to pull the lucida fonts > out automatically and drop them in, please don't use > the name plan9port to describe the resulting software. > i don't want any part of it. >=20 > thanks. > russ