svn commit: r482482 - head/x11-fonts/liberation-fonts-ttf

Tobias Kortkamp tobik at FreeBSD.org
Sat Oct 20 15:19:39 UTC 2018


On Sat, Oct 20, 2018, at 17:02, Thierry Thomas wrote:
> Le sam. 20 oct. 18 à 15:21:58 +0200, Tobias Kortkamp <tobik at FreeBSD.org>
>  écrivait :
> 
> > > Yes, there is, but a GH_DISTNAME macro is missing from our GH_ stuff,
> > > and I do not want to handle a specific MASTER_SITES for that.
> > 
> > So everyone is forced to live with additional build dependencies
> > for a tiny bit of extra maintainer convenience?  :-(
> > 
> > Building fontforge is not something you'd have to do to build a
> > package set for a FreeBSD desktop normally.
> 
> BUILD_DEPENDS do not belong to a packages set!

Yes, I do not have to install BUILD_DEPENDS on a desktop after the
liberation-fonts-ttf package has been built, but that is missing
the point.  Of course build dependencies have to have been previously
built to be able to use them to build liberation-fonts-ttf. They are also
part of the package repository afterwards. :-(

> > > Furthermore it is now possible to get other formats (woff, etc.) if
> > > someone needs them.
> > 
> > Has someone actually requested it? Anyway this could be a non-default
> > option in the port.
> 
> Not yet, and upstream do not build them by default, but Web Open Font
> Format (WOFF) is a W3C recommendation.
> 
> This is a good case for multi-packages, and I'd like to add it when it
> will be available.
> 
> > > The disadvantage is only some BUILD_DEPENDS for ports builders, but
> > > these are light ports.
> > 
> > These things add up fast.
> 
> OK, I've just added an item to my TODO-list:
> - use something like GH_DISTNAME with USE_GITHUB is set.

How would this be different than just setting MASTER_SITES and be
done with it?

I'm attaching the patch I have in my ports tree fork now.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: liberation-fonts-ttf.diff
Type: text/x-patch
Size: 1951 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/svn-ports-all/attachments/20181020/90882fd2/attachment.bin>


More information about the svn-ports-all mailing list