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: <3BF2F6E7.96D26EC@wapme-systems.de>
Date: Wed, 14 Nov 2001 23:57:43 +0100
From: Stipe Tolj <tolj AT wapme-systems DOT de>
Organization: Wapme Systems AG
X-Mailer: Mozilla 4.7 [de]C-CCK-MCD QXW0322b  (WinNT; I)
X-Accept-Language: de,en
MIME-Version: 1.0
To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
CC: cygwin-apps AT sources DOT redhat DOT com
Subject: Re: [FYI] file conflicts in recent Cygwin packages (see syscheck.log)
References: <3BF2982D DOT 3D963F7C AT wapme-systems DOT de> <035401c16d4b$c2127990$0200a8c0 AT lifelesswks> <3BF2EF6E DOT 560EF0D0 AT wapme-systems DOT de> <050401c16d5c$a5e79140$0200a8c0 AT lifelesswks>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

> > who is going to advice the package maintainers to check for these file
> > conflicts?!
> 
> Well if we can lint the packages at upload time, I guess Chris will get
> the failure message (Chris, I'm happy to be copied on that if you want).
> Otherwise, I think you(Stipe)'ll have to do it for now.

I would like to do so. Is there any reference who (i.e. which person)
is responsible for which package?!

Maybe an database would help here to keep track of maintainers for
certain packages and even more for "bug reporting" concerning the
single packages. The maintainer would have the chance to see if users
have notices problems with her/his package and react to realease a new
cycle.

> Do you mean that if one package is dependent on another, you will
> announce the conflict, and if they are not you won't?

The file conflict is currently always announced. Semanticaly a file
conflict between related (dependable) packages is less worse than a
file conflict between unrelated packages. We assume that a usage of a
specific file between two unrelated packages has more potential for
problems. I guess this is obvious.

> Yes, sort of, see "package naming". I don't see that we need to enforce
> one or other compression format right now.

this is true -- I'm only peaking on packages that become really big,
like the xfree86 packages or others. bzip2 is noticable better here.


Stipe

tolj AT wapme-systems DOT de
-------------------------------------------------------------------
Wapme Systems AG

Münsterstr. 248
40470 Düsseldorf

Tel: +49-211-74845-0
Fax: +49-211-74845-299

E-Mail: info AT wapme-systems DOT de
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are