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: Thu, 06 Aug 2020 20:05:34 +0900 [thread overview]
Message-ID: <20200806200531.9F3E.50F79699@gmail.com> (raw)
In-Reply-To: <1056335e-ed02-e4a0-3c2c-0820c861c324@gmail.com>
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/
> >
> > ( forked for cygwin build to
> > https://github.com/cygwin-lem/fontforge/tree/n_20200314p64_maybe-nonbreaking )
> >
> > And, some of Yaakov's patches are now in the upstream:
> > https://github.com/fontforge/fontforge/commit/c0a27e4bdc436e73901b7a6cd7e4b6910fcee408
> >
> >
> > * Cygport files are forked here:
> > https://github.com/cygwin-lem/fontforge-cygport/tree/n_20200314p64-1
> > from
> > https://cygwin.com/git/cygwin-packages/fontforge.git .
> >
> >
> > * New test package files are here:
> > https://cygwin-lem.github.io/fontforge-cygport/ .
> >
> >
> > ========
> > * Note:
> >
> > To build test packages:
> >
> > (1) prepare cmake-3.17.3-1 (test)
> >
> > (2) invoke build.sh under
> > https://github.com/cygwin-lem/fontforge-cygport/tree/n_20200314p64-1
> > as follows:
> >
> > ./build.sh --generate-cygport --download --test
> >
> > (or for short: "./build.sh -s -d -t" ).
> >
> > This generates cygport files, downloads a source tarball, and test-tagged builds.
> >
> >
> > When we build fontforge, it can be linked to only one specific
> > version of python3.
> > So, I've prepared four cygport files by a script ./build.sh
> >
> > fontforge-nopy.cygport
> > fontforge-py38.cygport
> > fontforge-py37.cygport
> > fontforge-py36.cygport
> >
> > ========
> > * Need help
> >
> > Please give me any advice on building and packaging such cases...
> >
> >
> > ========
> > * Need help more
> >
> > Any advice on how to adapt it to the CI system.
> > Is it enough just putting the generated cygport files in a repository?
> >
> >
> >
> > Regards,
> >
> > Lem
> >
> Thanks Lem
>
> on my TODO list for the weekend, assuming no oneelse do it before
>
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.
--
Lem
next prev parent reply other threads:[~2020-08-06 11:05 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 [this message]
2020-08-06 11:19 ` marco atzeri
2020-09-20 2:51 ` Lemures Lemniscati
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=20200806200531.9F3E.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).