public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] libuninameslist-20200413-1, python-libuninameslist-0.2-1
Date: Sat, 01 Aug 2020 12:08:31 +0900	[thread overview]
Message-ID: <20200801120828.1529.50F79699@gmail.com> (raw)
In-Reply-To: <20200710191859.CE22.50F79699@gmail.com>

Date: Fri, 10 Jul 2020 19:19:01 +0900
From: Lemures Lemniscati

> Date: Thu, 9 Jul 2020 20:46:43 +0200
> From: Marco Atzeri via Cygwin-apps <cygwin-apps@cygwin.com>
> 
> > On 09.07.2020 14:13, Lemures Lemniscati via Cygwin-apps wrote:
> > > Date: Thu, 09 Jul 2020 00:30:53 +0900
> > > From: Lemures Lemniscati
> > >
> > >> Hi!
> > >>
> > >> Current Cygwin packages of LibUniNamesList are very old (updated almost 7 years ago).
> > >> Now, the upstream sources are maintained at https://github.com/fontforge/libuninameslist
> > >> and able to treat Unicode 13.0.
> > >>
> > >> Cygport files are forked here: https://github.com/cygwin-lem/libuninameslist-cygport/tree/w_20200413
> > >> from http://cygwin.com/git/cygwin-packages/libuninameslist .
> > >>
> > 
> > by default we now install only the dynamic and not the static
> > so you should remove/not build the
> > 
> > usr/lib/libuninameslist-fr.a
> > usr/lib/libuninameslist.a
> > 
> > and install only
> > 
> > usr/lib/libuninameslist-fr.dll.a
> > usr/lib/libuninameslist.dll.a
> > 
> > these should not go in the libuninameslist1
> > 
> > usr/share/doc/libuninameslist/AUTHORS
> > usr/share/doc/libuninameslist/ChangeLog
> > usr/share/doc/libuninameslist/COPYING
> > usr/share/doc/libuninameslist/LICENSE
> > usr/share/doc/libuninameslist/README
> > 
> > my suggestion, put them in the devel package.
> > 
> > I know that Yaakov installed them, but normally the
> > library package contains only the libraries
> > 
> > I have not tested the python-* , but I see no reason to build the 35.
> > (personal opinion)
> 
> Thank you, Macro, for reviewing !
> 
> Updated test package files are here as before:
>   https://cygwin-lem.github.io/libuninameslist-cygport/index.html .
> 
> A color diff of the cygport files is attached as an HTML file.
> 

Since there seems to be no demand for python-libuninameslist-*,
I've removed it and refreshed libuninameslist.cygport
to just update the library.


The new cygport file is forked here
  https://github.com/cygwin-lem/libuninameslist-cygport/tree/w_20200413p3
from http://cygwin.com/git/cygwin-packages/libuninameslist .

Updated test package files are here as before:
  https://cygwin-lem.github.io/libuninameslist-cygport/

========
* Note:

This library is to be linked from fontforge.

Please, review it for ITA, again.


Regards,

Lem

  reply	other threads:[~2020-08-01  3:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08 15:30 Lemures Lemniscati
2020-07-09 12:13 ` Lemures Lemniscati
2020-07-09 18:46   ` Marco Atzeri
2020-07-10 10:19     ` Lemures Lemniscati
2020-08-01  3:08       ` Lemures Lemniscati [this message]
2020-08-02  6:10         ` Marco Atzeri
2020-08-02 10:32           ` 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=20200801120828.1529.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).