On 04/10/2012 01:05, Larry Hall (Cygwin) wrote:
Well it has to use something to validate the package. The data it
uses is the list of files in the .lst.gz file you deleted. So it
can't do allot of validating without that metadata.
Indeed.
But I suppose it would make sense to not return "OK" i
On 10/3/2012 6:02 PM, Vincent Rivière wrote:
On 01/10/2012 13:24, marco atzeri wrote:
cygcheck -c
I wonder how much "cygcheck -c" is reliable.
For example, the libmpfr4 package.
I delete /bin/cygmpfr-4.dll and /etc/setup/libmpfr4.lst.gz
As a result, I can't compile sources with gcc anymore
On 01/10/2012 13:24, marco atzeri wrote:
cygcheck -c
I wonder how much "cygcheck -c" is reliable.
For example, the libmpfr4 package.
I delete /bin/cygmpfr-4.dll and /etc/setup/libmpfr4.lst.gz
As a result, I can't compile sources with gcc anymore due to the missing
cygmpfr-4.dll.
But "cygc
On 10/1/2012 1:38 PM, Vincent Rivière wrote:
On 01/10/2012 13:24, marco atzeri wrote:
cygcheck -c
Thanks, this is what I looked for.
However, I notice that:
1) If the .lst.gz file is missing, "cygcheck -c " still reports
OK.
a package with a missing .lst.gz , should be a obsolete and empt
On 01/10/2012 13:24, marco atzeri wrote:
cygcheck -c
Thanks, this is what I looked for.
However, I notice that:
1) If the .lst.gz file is missing, "cygcheck -c " still reports OK.
2) When testing a missing package, "cygcheck -c " does not
output any status line, but its return code is stil
On 10/1/2012 1:03 PM, Vincent Rivière wrote:
Hello.
I would like to know how to reliably test if a Cygwin package is already
installed (just like setup.exe does).
Currently, I test the existence of /etc/setup/.lst.gz. It works
perfectly for me, but a user reported to me that that file was missi
6 matches
Mail list logo
