Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <06e601c16e2c$bad3e5b0$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Stipe Tolj" <tolj AT wapme-systems DOT de>
Cc: "Charles Wilson" <cwilson AT ece DOT gatech DOT edu>,
   "Gerrit P. Haase" <cygwin AT cygwin DOT com>
References: <5314439342 DOT 20011114212805 AT familiehaase DOT de>	 <3BF2D797 DOT B0481987 AT ece DOT gatech DOT edu> <20011114211942 DOT GB9636 AT redhat DOT com> <1119104841 DOT 20011114224550 AT familiehaase DOT de> <3BF2F6AD DOT 726DB93E AT ece DOT gatech DOT edu> <3BF3C5A2 DOT 7F7907B8 AT wapme-systems DOT de> <05cc01c16e24$2e03bf00$0200a8c0 AT lifelesswks> <3BF44D66 DOT A282870F AT wapme-systems DOT de>
Subject: Re: new site for my ports is up
Date: Fri, 16 Nov 2001 10:24:52 +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: 15 Nov 2001 23:23:02.0108 (UTC) FILETIME=[786C89C0:01C16E2C]


----- Original Message -----
From: "Stipe Tolj" <tolj AT wapme-systems DOT de>
To: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
Cc: "Charles Wilson" <cwilson AT ece DOT gatech DOT edu>; "Gerrit P. Haase"
<cygwin AT cygwin DOT com>
Sent: Friday, November 16, 2001 10:19 AM
Subject: Re: new site for my ports is up


> > The site maintenance is actually pretty automatic now. Copy the file
to
> > the location, it's included. Delete the file, it's removed. Hmm
that's
> > easy :}.
>
> yes, considered in the raw uploading semantic. But what about
> regression testing and file conflicts. Basicly we tread tarballs as
> black-boxes without knowing (exactly) if the included files may mess
> up a installation/package in some way.

And? File conflicts we've discussed. They are bad while setup can't
detect them, but after that they are ok.
Any package linting we do _can not_ assume that all packages are stored
at redhat.com. Folk have local packages that they just drop in their
install tree, and we cannot predict what is in them. Therefore such
package linting is independent of the contents of the redhat master
site.

> I can't find that, what subject was the thread running under?

I dunno, check cygwin-apps, cgf for the last week.

> > Hmm, I don't agree. See my point about conflicts. Conflicts are
normal,
> > and to be expected. There is no point getting all automated about
> > detecting conflicts in packages until setup.exe can prevent the
users
> > installing those conflicting packages. Until that point, a check
every
> > month or three will probably suffice. An automated check on the
package
> > when it is put into the repository would also be great, but that
takes
> > tuit and I can think of other things that I'd like Chris to tuit
before
> > this (winsup/utils breakout specifically).
>
> I agree, a fully automated procedure is not what I'm intending, but a
> automation _support_.

I think I'm confused. You talked about a automatic upload + error
reporting system...

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/