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:	<05cc01c16e24$2e03bf00$0200a8c0@lifelesswks>
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Stipe Tolj" <tolj AT wapme-systems DOT de>,
	"Charles Wilson" <cwilson AT ece DOT gatech DOT edu>
Cc:	"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>
Subject:	Re: new site for my ports is up
Date:	Fri, 16 Nov 2001 09:23:40 +1100
MIME-Version:	1.0
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 22:21:49.0961 (UTC) FILETIME=[EBA75F90:01C16E23]

----- Original Message -----
From: "Stipe Tolj" <tolj AT wapme-systems DOT de>


> The only point I have to critic is the lack in tools and mechanisms to
> maintain the packages "on the distribution" (site). I would like to
> see an integrated web site that focuses on two aims:

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

>   1) supporting the (new) users the best way to get what they want,
> aka "has someone ported foobar already to Cygwin?!"

Chris has this already - he generates an automatic list of packages on
the cygwin site. See this list a few days back IIRC.

>   2) support the pacakge maintainers, i.e. by having a reference of
> all used files and possible file conflicts within a database on the
> site. A package maintainer should be able to "check-in" a new release
> and roll a regression test on it before it gets publicaly available
> and integrated to setup.ini.

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

> > Some stuff cannot be distributed from the cygwin mirror system, for
> > legal or political reasons (think cygipc).  [BTW, Gerrit, I have NO
> > problems with you mirroring the cygipc package. Go ahead.  But don't
try
> > to submit it for inclusion in the official dist, 'cause it won't be
> > accepted]
>
> why is that?

cygipc is getting replaced (slowly) by a cygwin-integrated ipc daemon.
(BTW: chris, can you comment on the file layout for that, so that it can
be merged.)

As for other things, it's a case by case basis. Imagine a package that
has legal issues with being distributed from the US, for example.

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/

- Raw text -