public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] perl-Image-ExifTool
Date: Tue, 16 Nov 2021 10:01:34 -0700	[thread overview]
Message-ID: <c74817fb-e1eb-1142-6bbd-2c1a78eebd41@SystematicSw.ab.ca> (raw)
In-Reply-To: <87r1bga0h9.fsf@Rainer.invalid>

On 2021-11-16 02:55, Achim Gratz wrote:
> Brian Inglis writes:
>> This perl module is not built from CPAN as that is 5 releases out of
>> date 12.30 from the repo release 12.35.
> 
> NACK.  We do not package development releases unless absolutely
> necessary.  The latest production release is 12.30 (Phil only seems to
> mirror production releases to CPAN).  Anyway, I'll have a look if it
> builds cleanly and if so will ITP it myself.
> 
>> The cygport and tarballs are available online at:
>>
>> https://drive.google.com/drive/folders/1PwBaANQ2fnagJG8zebp0pN1qYujSBP0j

I noticed that the html was not packaged above and added DOCS=html, as 
the number of supported file types, tags, and options benefit from the 
expanded explanations.

> Get rid of that Google drive nonsense here, please.

Where else can one post package tarballs for review?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

      parent reply	other threads:[~2021-11-16 17:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16  7:42 Brian Inglis
2021-11-16  9:55 ` Achim Gratz
2021-11-16 13:55   ` Achim Gratz
2021-11-16 16:55     ` Brian Inglis
2021-11-17 10:32     ` Marco Atzeri
2021-11-16 17:01   ` Brian Inglis [this message]

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=c74817fb-e1eb-1142-6bbd-2c1a78eebd41@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).