public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Joel Breazeale <joel.breazeale@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Package Install Date
Date: Wed, 08 Jun 2016 21:29:00 -0000	[thread overview]
Message-ID: <CALUJTM6182D4x09S3=_8c8eET_17RVqk31UTd9JDG0-Jyp_Rqg@mail.gmail.com> (raw)
In-Reply-To: <87porrtq88.fsf@Rainer.invalid>

Thank you for your reply Achim!  I tried your suggestion and it was
much faster than my kludge!  There is one nit though, that libpopt0
shows up under cygcheck -c but is not present in
/etc/setup/libpopt0.lst.gz.  Also, under cygcheck -l libpopt0 has no
files.  One would think if I want to find all the installed packages
that cygcheck would be the source of truth!  As a workaround I can
ignore any cygcheck entry that doesn't have a corresponding file in
/etc/setup.  If there is any concern from anyone about the mismatch of
cygcheck and /etc/setup contents I would be glad to share details.

On Wed, Jun 8, 2016 at 2:50 PM, Achim Gratz <Stromeko@nexgo.de> wrote:
> Joel Breazeale writes:
>> I am looking for a clean way to determine the install date/time for a
>> Cygwin package.  I have a hack that suffices, just want to see what
>> alternatives exist.  Thanks!
>
> Provided nothing messes with the clock and the timestamps, look at the
> mtime of /etc/setup/pkgname.lst.gz (it's produced by setup during
> installation).
>
>
> Regards,
> Achim.
> --
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
>
> SD adaptation for Waldorf rackAttack V1.04R1:
> http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2016-06-08 21:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08 19:25 Joel Breazeale
2016-06-08 19:50 ` Achim Gratz
2016-06-08 21:29   ` Joel Breazeale [this message]
2016-06-08 22:09     ` Ken Brown
2023-09-13 17:57       ` Joel Breazeale
     [not found] ` <1796655579.20160608224630@yandex.ru>
2016-06-09 14:47   ` Joel Breazeale
2016-06-09 19:22     ` Achim Gratz

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='CALUJTM6182D4x09S3=_8c8eET_17RVqk31UTd9JDG0-Jyp_Rqg@mail.gmail.com' \
    --to=joel.breazeale@gmail.com \
    --cc=cygwin@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).