Mail Archives: cygwin-apps/2001/11/11/00:00:12
On Sun, Nov 11, 2001 at 03:54:43PM +1100, Robert Collins wrote:
>
>----- Original Message -----
>From: "Christopher Faylor" <cgf AT redhat DOT com>
>To: <cygwin-apps AT cygwin DOT com>
>Sent: Sunday, November 11, 2001 3:40 PM
>Subject: Re: Move zlib up one level?
>
>
>> On Sun, Nov 11, 2001 at 03:37:26PM +1100, Robert Collins wrote:
>> >
>> >----- Original Message -----
>> >From: "Christopher Faylor" <cgf AT redhat DOT com>
>> >
>> >
>> >> >Yeah, but isn't cygcheck a cygwin1.dll application?
>> >> The only problem is that I had to pull a lot of code out of
>setup.exe.
>> >
>> >Not good.. particularly with the amount of changes I'm accruing in
>setup
>> >at the moment.
>>
>> You're not planning on changing any of the files in /etc/setup are
>you?
>> That would be a bad thing(TM).
>
>Not directly or immediately. And certainly any changes I do suggest will
>be done in a backward compatible fashion..
>
>There are some things I believe we should be able to do with
>/etc/setup...
>1) Detect cross-package conflicts. Say foo and bar both contain
>/usr/bin/ld.exe.
>2) The lst files are currently gz' files, I think it would be good to
>change to using bz2 in the future.
>
>Doing the 1st one really requires a more database orientated approach --
>long term of course.
Right. But in the meantime we have a huge user base who can't easily
figure out what packages they have installed.
>> Also, since I wrote most (all?) of what I'm pulling out, I felt pretty
>> comfortable with it...
>
>Oh, sure :}. I wasn't meaning you weren't capable, just that having the
>same code in two places is bad because of the capability for skew.
Absolutely. I really hate this but I was doing it the wrong way for 1.3.5.
I am optimistically thinking that there won't be a new cygwin release for
a while after that and I wanted to get something that works into 1.3.5.
I also didn't want to be pulling things apart while you are actively working
on this but maybe this is an important enough goal that it is worth doing
ASAP.
Btw, I considered just suggesting that this functionality should go into
setup.exe. It would be sort of nice to be able to say:
setup --dump
or something to get the current list of installed packages.
However, there are two problems with that, IMO:
1) setup.exe is currently a windows app so it can't write to the console.
2) Cygcheck should really be the one stop place for all debugging output
so, at the very least, cygcheck would have to call a 'dump capable'
setup.exe to get its output but, that wouldn't be useful for debugging
cases where setup.exe wasn't available.
cgf
- Raw text -