On 29/09/2017 21:16, Sam Edge (Cygwin) wrote:
Hi all.
I've been developing a Python package that can interrogate and
manipulate local package caches (the directories where setupXXX.exe
keeps its downloads) and installation databases (from Cygwin
/etc/setup/installed.db files) with a mind to prun
On 30/09/2017 12:23, Andrey Repin wrote:
>
>> Indeed. However, while off label usage of Cygwin is anathema to me but
>> sometimes I wish 'base' wasn't quite so big and have to pare things down
>> a little once installed, e.g. as part of a makefile- and/or
>> Eclipse-based build tree in source code
Greetings, Sam Edge!
>>> It's not production ready yet but it's already flagged up some issues.
>>> For example we have lots of dependency loops in the 'requires' fields in
>>> setup.ini - even to the point that some packages depend upon themselves!
>> Dependency upon itself is curious, but other
Hi Andrey.
Nice to be back in a thread with such esteemed folk. ;-)
On 30/09/2017 10:00, Andrey Repin wrote:
> Greetings, Sam Edge (Cygwin)!
>
>> I've been developing a Python package that can interrogate and
>> manipulate local package caches (the directories where setupXXX.exe
>> keeps its down
Greetings, Sam Edge (Cygwin)!
> I've been developing a Python package that can interrogate and
> manipulate local package caches (the directories where setupXXX.exe
> keeps its downloads) and installation databases (from Cygwin
> /etc/setup/installed.db files) with a mind to pruning, merging and
>
On 30/09/2017 00:39, Steven Penny wrote:
On Fri, 29 Sep 2017 21:16:17, "Sam Edge (Cygwin)" wrote:
For example we have lots of dependency loops in the 'requires' fields in
setup.ini - even to the point that some packages depend upon themselves!
It is the job of the package manager to detect and
On 29/09/2017 23:39, Steven Penny wrote:
> On Fri, 29 Sep 2017 21:16:17, "Sam Edge (Cygwin)" wrote:
>> For example we have lots of dependency loops in the 'requires' fields in
>> setup.ini - even to the point that some packages depend upon themselves!
>
> It is the job of the package manager to det
On Fri, 29 Sep 2017 17:53:52, Doug Henderson wrote:
mintty is a windows, non-cygwin, executable
No, its not:
$ cygcheck mintty
Found: C:\cygwin64\bin\mintty.exe
C:\cygwin64\bin\mintty.exe
C:\cygwin64\bin\cygwin1.dll
which does not depend on cygwin1.dll
Yes, it does:
$ ldd /bin/mintty.exe
On 29 September 2017 at 14:16, Sam Edge (Cygwin) wrote:
> … mintty doesn't
> depend upon anything - it has no requires field. …
mintty is a windows, non-cygwin, executable which does not depend on cygwin1.dll
There are a few other such programs, which (I guess) are built using
the mingw32 tools
On Fri, 29 Sep 2017 21:16:17, "Sam Edge (Cygwin)" wrote:
For example we have lots of dependency loops in the 'requires' fields in
setup.ini - even to the point that some packages depend upon themselves!
It is the job of the package manager to detect and avoid such loops. No database
is perfect
10 matches
Mail list logo
