On 2016/11/16 15:40:48, pkx166h wrote:
On 2016/11/16 14:35:05, trueroad_trueroad.jp wrote: > > But, I think that the simplest way is to distribute the tarball at
the
> LilyPond site. > > e.g. > > >
http://lilypond.org/downloads/gub-sources/urw-fonts/urw-core35-fonts-79bcdfb.tar.gz
> > > > And change the warning message of configure script. > > e.g. > > (download tarball from > > >
http://lilypond.org/downloads/gub-sources/urw-fonts/urw-core35-fonts-79bcdfb.tar.gz
> > and extract it under '~/.local/share/fonts' etc., or use
--with-urwotf-dir)
> > I've made `urw-core35-fonts-79bcdfb.tar.xz`. >
https://drive.google.com/file/d/0ByGBX3PDrqjsbm9TOWktWjFCRmM/view?usp=sharing
> > If someone uploads it as >
`http://lilypond.org/downloads/gub-sources/urw-fonts/urw-core35-fonts-79bcdfb.tar.xz`,
> I will upload Patch Set 2 to Rietveld for changing the warning
message.
> > Or should I push the current Patch Set 1?
Push patch set 1. Then we can worry about getting the download up to
LilyPond
site afterwards. I will create a tracker to document all this.
James
https://sourceforge.net/p/testlilyissues/issues/4998/ has been created to document these changes. james https://codereview.appspot.com/315850043/ _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
