Bug#786971: [Pkg-fonts-devel] Bug#786971: Bug#786971: Bug#786971: fonts-roboto: build from source, new upstream

2017-01-03 Thread Paul Wise
On Wed, Jan 4, 2017 at 9:41 AM, James Godfrey-Kittle wrote: > Well, I suppose that makes sense since there is the option to build the > fonts. However I must point out that having sources for fonts is unusual > (probably because the distinction between source and binary is less clear > than with

Bug#786971: [Pkg-fonts-devel] Bug#786971: Bug#786971: fonts-roboto: build from source, new upstream

2017-01-03 Thread Paul Wise
On Wed, Jan 4, 2017 at 7:33 AM, James Godfrey-Kittle wrote: > It might be worth noting that prebuilt fonts now exist on the Roboto github > page: https://github.com/google/roboto/releases > > Roboto is constantly being updated with fixes, so if you ever feel inspired > to update the Debian

Bug#786971: [Pkg-fonts-devel] Bug#786971: fonts-roboto: build from source, new upstream

2015-06-01 Thread Vasudev Kamath
Hi Paul, Paul Wise p...@debian.org writes: Package: fonts-roboto Severity: wishlist It would be nice if fonts-roboto could be built from source now that Google actually made Roboto open source and released source/build stuff:

Bug#786971: [Pkg-fonts-devel] Bug#786971: fonts-roboto: build from source, new upstream

2015-06-01 Thread Paul Wise
On Mon, 2015-06-01 at 12:28 +0530, Vasudev Kamath wrote: Currently fonts-roboto is part of fonts-android using separate upstream means splitting roboto out of fonts-android source and make separate package. Obviously splitting fonts-roboto into a new fonts-roboto source package is the correct

Bug#786971: fonts-roboto: build from source, new upstream

2015-05-27 Thread Paul Wise
Package: fonts-roboto Severity: wishlist It would be nice if fonts-roboto could be built from source now that Google actually made Roboto open source and released source/build stuff: http://google-opensource.blogspot.com/2015/05/roboto-googles-signature-font-is-now.html