Quoting Daniel Kahn Gillmor (dkg@fifthhorseman.net): > I'm not really sure what to do about this other than to open an RC > bug against fontforge, which this e-mail should do :( > > We could probably make a new dfsg-free "clean" upstream tarball that > is still capable of building fontforge binaries by ripping out big > chunks of this file (i haven't tried it yet), but i don't know what > that would do to fontforge's ability to do Type1 font generation. > > Another approach would be to move fontforge from the main archive to > the non-free archive; but it seems like that would relegate many of > our font packages to contrib, due to build-dependencies. :( > > I'm open to other suggestions; i would be overjoyed, in fact, to > hear other suggestions. Does anyone have any proposals? I guess you intend to raise the issue in upstream's mailing list?
Attachment:
signature.asc
Description: Digital signature