From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] fontforge-{nopy,py38,py37,py36}-20200314p64-1 for review
Date: Sun, 20 Sep 2020 11:51:24 +0900 [thread overview]
Message-ID: <20200920115120.8A86.50F79699@gmail.com> (raw)
In-Reply-To: <CAB8Xom877Ro-6ko2hJeuAqommnUB-AqMkUC6tPH2VmedXKqEqQ@mail.gmail.com>
On Thu, 6 Aug 2020 13:19:04 +0200, marco atzeri via Cygwin-apps
> On Thu, Aug 6, 2020 at 1:05 PM Lemures Lemniscati via Cygwin-apps wrote:
> >
> > On Fri, 31 Jul 2020 06:23:36 +0200, Marco Atzeri via Cygwin-apps
> > > On 30.07.2020 22:39, Lemures Lemniscati via Cygwin-apps wrote:
> > > > I'm trying to build fontforge packages with latest upstream
> > > > https://github.com/fontforge/fontforge/
> >
> > Packages related to fontforge 20190801 or 20200314 in Ubuntu, Debian and
> > Fedora are linked to python 3.8.
> >
> > https://packages.ubuntu.com/focal/python3-fontforge
> > https://packages.debian.org/bullseye/python3-fontforge
> > https://fedora.pkgs.org/32/fedora-x86_64/fontforge-20200314-3.fc32.x86_64.rpm.html
> >
> > So, I'll retry to make fontforge.cygport in order to link it python3.8 only,
> > later.
>
> that was also my finding. I agree on your proposal
>
> In addition it seems sphinx is "needed" for 3.8
> so I put it on my TODO list.
>
> > --
> > Lem
>
> unfortunately I have problem with python-gi, so other things are dragging on...
>
> Regards
> Marco
Hi!
** fontforge 20200314p70 linked with python 3.8 for review
I've rewritten fontforge.cygport and patches for cygwin
https://github.com/cygwin-lem/fontforge-cygport/tree/n_20200314p70-1 ,
for the latest upstream https://github.com/fontforge/fontforge/ .
New test packages are here: https://cygwin-lem.github.io/fontforge-cygport/ ,
or https://github.com/cygwin-lem/fontforge-cygport/tree/gh-pages .
Regards,
Lem
prev parent reply other threads:[~2020-09-20 2:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 20:39 Lemures Lemniscati
2020-07-31 4:23 ` Marco Atzeri
2020-08-06 11:05 ` Lemures Lemniscati
2020-08-06 11:19 ` marco atzeri
2020-09-20 2:51 ` Lemures Lemniscati [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200920115120.8A86.50F79699@gmail.com \
--to=lemures.lemniscati@gmail.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).