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] libexif-0.6.22-1
Date: Sun, 03 Jan 2021 11:46:18 +0900	[thread overview]
Message-ID: <20210103114614.387E.50F79699@gmail.com> (raw)
In-Reply-To: <877dovasx2.fsf@Rainer.invalid>

On Sat, 02 Jan 2021 23:13:45 +0100, Achim Gratz
> Lemures Lemniscati via Cygwin-apps writes:
> > I agree. And I'll remove the dependency and rebuild.
> 
> Minor nit: IMHO it would have been all-around cleaner if you obsoleted
> libexif-common and replaced it with libexif-doc.
>


I guess if we make libexif-doc package, it would be better to move html
document files (104 files), also, from libexiv-devel into libexif-doc.


So an expected libexiv-doc will contain

/usr/share/doc/libexif/ABOUT-NLS
/usr/share/doc/libexif/AUTHORS
/usr/share/doc/libexif/ChangeLog
/usr/share/doc/libexif/COPYING
/usr/share/doc/libexif/NEWS
/usr/share/doc/libexif/README
/usr/share/doc/libexif/SECURITY.md

and

/usr/share/doc/libexif/libexif-api.html/*

(104 files).

How about this rearrangement?

Lem


  reply	other threads:[~2021-01-03  2:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-30 23:33 Lemures Lemniscati
2020-12-31  2:07 ` Lemures Lemniscati
2020-12-31  8:04   ` Lemures Lemniscati
2020-12-31  8:44     ` Achim Gratz
2020-12-31  8:49       ` Achim Gratz
2020-12-31  9:32         ` Lemures Lemniscati
2020-12-31 10:54           ` Lemures Lemniscati
2020-12-31 15:44             ` Marco Atzeri
2020-12-31 22:22               ` Lemures Lemniscati
2021-01-02 22:13                 ` Achim Gratz
2021-01-03  2:46                   ` Lemures Lemniscati [this message]
2021-01-03  3:22                     ` Marco Atzeri
2021-01-03  9:51                     ` Achim Gratz
2021-01-04 13:58                       ` 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=20210103114614.387E.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).