* Package Install Date
@ 2016-06-08 19:25 Joel Breazeale
2016-06-08 19:50 ` Achim Gratz
[not found] ` <1796655579.20160608224630@yandex.ru>
0 siblings, 2 replies; 7+ messages in thread
From: Joel Breazeale @ 2016-06-08 19:25 UTC (permalink / raw)
To: cygwin
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!
--
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Package Install Date
2016-06-08 19:25 Package Install Date Joel Breazeale
@ 2016-06-08 19:50 ` Achim Gratz
2016-06-08 21:29 ` Joel Breazeale
[not found] ` <1796655579.20160608224630@yandex.ru>
1 sibling, 1 reply; 7+ messages in thread
From: Achim Gratz @ 2016-06-08 19:50 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 7+ messages in thread
[parent not found: <1796655579.20160608224630@yandex.ru>]
* Re: Package Install Date
[not found] ` <1796655579.20160608224630@yandex.ru>
@ 2016-06-09 14:47 ` Joel Breazeale
2016-06-09 19:22 ` Achim Gratz
0 siblings, 1 reply; 7+ messages in thread
From: Joel Breazeale @ 2016-06-09 14:47 UTC (permalink / raw)
To: cygwin
Andrey,
My goal is to build a list of all the installed packages in
chronological order. With such a list I can see which package were
installed beyond the initial set. The reason for this is to be able
to tell a colleague what to install to get their Cygwin configured
like mine so they can use tools I've created.
I was hoping a package install date/time would be provided by the
package management system. Absent an official package install
date/time I'll take whatever I can scrounge up! A stat of <package>
in /etc/setup/<package>.lst.gz gives me a "Birth" date/time which is
sufficient for my purposes. For example:
$ pkginstalldate 2>/dev/null | sort
. . .
2016-05-24 13:28:27.839145400 -0500 xproto
2016-05-24 13:28:27.937145400 -0500 zlib-devel
2016-05-24 13:28:27.958145400 -0500 znc
2016-05-24 13:28:28.302145400 -0500 znc-perl
2016-05-25 08:52:38.208000000 -0500 m4
2016-05-26 11:07:30.588000000 -0500 vim
2016-05-26 11:07:30.692000000 -0500 vim-common
2016-05-26 11:07:33.714000000 -0500 xxd
2016-06-06 14:31:01.692765800 -0500 girepository-GdkPixbuf2.0
2016-06-06 14:31:01.708365700 -0500 girepository-Gst1.0
2016-06-06 14:31:01.724965600 -0500 girepository-GstInterfaces1.0
2016-06-06 14:31:01.803965100 -0500 libcroco0.6_3
2016-06-06 14:31:01.803965100 -0500 libfontconfig-common
2016-06-06 14:31:01.879364700 -0500 libfontconfig-devel
2016-06-06 14:31:01.911564500 -0500 libfontconfig1
2016-06-06 14:31:01.927164400 -0500 libgailutil18
2016-06-06 14:31:01.942764300 -0500 libgdk_pixbuf2.0-devel
2016-06-06 14:31:01.943764300 -0500 libgdk_pixbuf2.0_0
2016-06-06 14:31:02.263162400 -0500 libglib2.0-devel
2016-06-06 14:31:02.756159400 -0500 libglib2.0_0
2016-06-06 14:31:03.294556500 -0500 libgstinterfaces1.0_0
2016-06-06 14:31:03.356956100 -0500 libgstreamer1.0_0
2016-06-06 14:31:03.524955100 -0500 libgtk2.0-devel
2016-06-06 14:31:03.941952600 -0500 libgtk2.0_0
2016-06-06 14:31:04.804547500 -0500 libhdf5hl_10
2016-06-06 14:31:04.809547500 -0500 liborc0.4_0
2016-06-06 14:31:04.850747300 -0500 libpq5
2016-06-06 14:31:04.866347200 -0500 perl-B-Generate
2016-06-06 14:31:04.881947100 -0500 perl-Capture-Tiny
2016-06-06 14:31:04.897547000 -0500 perl-Config-Perl-V
2016-06-06 14:31:04.898547000 -0500 perl-ExtUtils-MakeMaker
2016-06-06 14:31:05.054346200 -0500 perl-HTTP-Tiny
2016-06-06 14:31:05.104145900 -0500 perl-List-AllUtils
2016-06-06 14:31:05.119745800 -0500 perl-List-MoreUtils
2016-06-06 14:31:05.152945600 -0500 perl-List-SomeUtils
2016-06-06 14:31:06.376138400 -0500 unzip
The above helps me to remember I installed m4, vim and unzip beyond my
initial setup.
[I use /dev/null because of libpopt0 as mentioned in earlier
discussion. I haven't quite gotten to the point where I feel
comfortable ignoring the error generated for it.]
--Joel
On Wed, Jun 8, 2016 at 2:46 PM, Andrey Repin <anrdaemon@yandex.ru> wrote:
> Greetings, Joel Breazeale!
>
>> 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!
>
> How do you define this "install date" ?
> The very first installation of any Cygwin package?
> %CYGROOT%/var/log/setup.log may contain this information.
> Or may not.
>
>
> --
> With best regards,
> Andrey Repin
> Wednesday, June 8, 2016 22:43:45
>
> Sorry for my terrible english...
>
--
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
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2023-09-13 17:57 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-06-08 19:25 Package Install Date Joel Breazeale
2016-06-08 19:50 ` Achim Gratz
2016-06-08 21:29 ` Joel Breazeale
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
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).