On 2020/06/01 11:00, Edd Barrett wrote: > Hi Chris, > > On Mon, Jun 01, 2020 at 10:04:22AM +0100, Chris Rawnsley wrote: > > FYI v2's term became v3's fixed. v3's term is more like v2's TermLig > > That's fine. > > > I got frustrated with CVS and just produced the patch by diff-ing two > > directories. Hope that's okay. > > That should be OK, but it'd be better to use a diff out of cvs though.
Or git with the conversion at github.com/openbsd/ports. > > This version includes slab for the purposes of just showing how subdir > > can work in this context. You can easily remove SUBDIR += slab from > > Makefile and the slab directory so that just the default family is in > > the update. > > Sorry to be a pain, but can you send a diff which does only the > update and without any structural changes to the port directories. > > As soon as you start moving things around in the ports tree, there are > implications for `pkg_add -u` (you would at least need some @pkgpath > markers in PLISTs). We don't want to get involved in that just yet. > > > Another change was to use the ttc files instead of ttf. That results in > > a much smaller footprint overall. Let me know if this is unacceptable. > > I don't know much about ttc fonts. Are they as widely supported as ttf? > If you want to replace ttf with ttc, at the very least they should work > with freetype/fontconfig and thus with common applications like xterm, > gimp, inkscape etc. ttc files hold a collection of ttf, and allow sharing common glyphs which can save a bunch of space. They have been supported by freetype/fontconfig for many years and there shouldn't be a problem using them.
