Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID: <016001c16a6f$16044fe0$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-apps AT cygwin DOT com>
References: <20011111032226 DOT GA21492 AT redhat DOT com> <3BEDFD26 DOT 7060806 AT ece DOT gatech DOT edu> <20011111043034 DOT GA22375 AT redhat DOT com> <013301c16a6a$90e52ae0$0200a8c0 AT lifelesswks> <20011111044025 DOT GB22496 AT redhat DOT com> <014601c16a6c$fb1dc910$0200a8c0 AT lifelesswks> <20011111045952 DOT GB22654 AT redhat DOT com>
Subject: Re: Move zlib up one level?
Date: Sun, 11 Nov 2001 16:09:47 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-OriginalArrivalTime: 11 Nov 2001 05:15:42.0691 (UTC) FILETIME=[E90C8330:01C16A6F]

----- Original Message -----
From: "Christopher Faylor" <cgf AT redhat DOT com>
> >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.

Perhaps a new view in setup - categories/full/partial/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.

Makes sense. Hopefully the daemon will go in immedaitely post 1.3.5, and
that will need a little ironing out I'm sure.

> 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.

As long as you're happy to rework cygcheck twice :].

> 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.

That's a small problem :}.

> 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.

I think cygcheck should have the functionality built in statically, just
the source shouldn't be split.

Rob