From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: duplicate between packages (libuninameslist)
Date: Sun, 2 May 2021 06:54:45 +0200 [thread overview]
Message-ID: <3b2b7a26-998f-1f0e-b6d0-46a59fb5cd47@gmail.com> (raw)
In-Reply-To: <20210502104704.FED5.50F79699@gmail.com>
On 02.05.2021 03:47, Lemures Lemniscati via Cygwin-apps wrote:
> On Tue, 27 Apr 2021 05:45:40 +0200, Marco Atzeri via Cygwin-apps
>
>> 2 usr/share/doc/libuninameslist/COPYING
>> 2 usr/share/doc/libuninameslist/LICENSE
>
> About libuninameslist (which I maintain), these files are contained in:
>
> libuninameslist0-20091231-1
> libuninameslist-devel-20200413p3-1
>
> When I updated libuninameslist packages, I've moved the files from
> libuninameslist[01] into libuninameslist-devel.
>
> So, duplication will last until libuninamelist0 is removed.
no big deal as they are the same file. it can wait the next release.
> To reduce the duplication, I should make libuninameslist0-20091231-2
> in some way (e.g. removing duplicated files, or renaming them).
it should contain only the dll; I found the style
libgdal28_CONTENTS="usr/bin/cyggdal-28.dll"
is useful to notice upstream API bump, that sometime they
forget to announce
> Regards,
>
> Lem
>
Regards
Marco
next prev parent reply other threads:[~2021-05-02 4:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 3:45 duplicate between packages Marco Atzeri
2021-05-01 21:48 ` Ken Brown
2021-05-02 1:47 ` duplicate between packages (libuninameslist) Lemures Lemniscati
2021-05-02 4:54 ` Marco Atzeri [this message]
2021-05-02 5:49 ` Achim Gratz
2021-05-04 17:13 ` duplicate between packages Jon Turney
2021-05-20 16:26 ` 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=3b2b7a26-998f-1f0e-b6d0-46a59fb5cd47@gmail.com \
--to=marco.atzeri@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).