public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps <cygwin-apps@cygwin.com>
Subject: Re: [ITA from Yaakov] freeport2
Date: Tue, 12 May 2020 14:34:31 -0400	[thread overview]
Message-ID: <393af1cd-d8a1-1270-8d34-df7e334c9b97@cornell.edu> (raw)
In-Reply-To: <5e20bed1-151a-93d8-c54f-182c91e0d2f4@gmail.com>

On 5/12/2020 2:08 PM, Marco Atzeri via Cygwin-apps wrote:
> Am 12.05.2020 um 18:53 schrieb Ken Brown via Cygwin-apps:
>> On 5/12/2020 12:50 PM, Ken Brown via Cygwin-apps wrote:
>>> My cygport file is attached.  Aside from some trivial URL changes, it differs 
>>> from Yaakov's as follows:
>>>
>>> 1. I've bumped the version from 2.9.1 to 2.10.2, the latest upstream release.
>>>
>>> 2. I removed the Fedora patch freetype-2.9-ftsmooth.patch, which is no longer 
>>> used in the Fedora build.
>>>
>>> 3. I removed the line 'cygmake refdoc', which was previously used to build 
>>> the API reference manual.  The html files are now included in the source 
>>> tarball. The refdoc target is apparently now only needed for a build from the 
>>> upstream git repo.
>>
>> Typo in the subject.  s/port/type/
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

> freeport2 is not in Cygwin for what I see
> 
> https://cygwin.com/packages/package_list.html
> 
> so may be it is a  ITP ?
> 
> Regards
> Marco
> 
> 

  reply	other threads:[~2020-05-12 18:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 16:50 Ken Brown
2020-05-12 16:53 ` Ken Brown
2020-05-12 18:08   ` Marco Atzeri
2020-05-12 18:34     ` Ken Brown [this message]
2020-05-12 19:00     ` Marco Atzeri
2020-05-12 18:02 ` [ITA from Yaakov] freetype2 Yaakov Selkowitz
2020-05-12 18:46   ` Ken Brown
2020-10-20 14:46     ` libfreetype CVE FYI Brian Inglis
2020-10-20 18:00       ` Ken Brown
2020-10-21 17:03         ` Achim Gratz
2020-10-21 21:20           ` Ken Brown

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=393af1cd-d8a1-1270-8d34-df7e334c9b97@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).