Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Message-ID: <028801c18044$90ce5fa0$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Charles Wilson" <cwilson AT ece DOT gatech DOT edu>,
   "Jan Nieuwenhuizen" <janneke AT gnu DOT org>
Cc: <cygwin-apps AT cygwin DOT com>
References: <m3667hsrm9 DOT fsf AT appel DOT lilypond DOT org><3C126412 DOT 1060903 AT ece DOT gatech DOT edu> <m3n10tqy1n DOT fsf AT appel DOT lilypond DOT org><3C1283D0 DOT 3090201 AT ece DOT gatech DOT edu> <m3wuzxp8y2 DOT fsf AT appel DOT lilypond DOT org>
Subject: Re: broken setup.hint files
Date: Sun, 9 Dec 2001 11:00:50 +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: 09 Dec 2001 00:00:45.0584 (UTC) FILETIME=[8D0FD100:01C18044]

----- Original Message -----
From: "Jan Nieuwenhuizen" <janneke AT gnu DOT org>


> >   Also, us normal cygwin maintainers CANNOT force the upstream
> > maintainers to use a sane naming scheme (see below).
>
> Ok, but cygwin could do some sanatising?  Some mainainers don't
> understand that package names don't have capitals (mysql?) or
spaces...

Cygwin packages are compared case insensitively.

...
> Ha, my tarball-sort gets this right:
Setup.exe is what matters :}. (No offense meant).

> where smart algorithms won't work.  Still, I haven't seen that
> situation in Cygwin, and I'm always looking for thing to do better,
> smaller or smarter.  Thought this was such a little thing too.

Squid has been through this. So has mingw.

> > It's not principle or want of time.  AFAICT, there is no mess.
>
> I would never have introduced bz2, or if I had, I would surely have
> run a small script like:
>
>     gzip -dc $foo.gz | bzip2> $foo.bz2

NO!!!. Let me repeat... NO!!!. One instance of that occuring caused
grief for weeks on the main mailing list, where setup wouldn't download
the .bz2 because the .gz existed, and wouldn't install the .gz because
it expected the .bz2.

Filenames for packages, once used must be unique. If any change,
including the extension or location is made, then the version number
MUST be incremented. We're dealing with a distributed database here -
the master setup.ini and all the replicated local install dirs.

> over the archive.  There are now two flavours of -src.tar.* packages.
> There are quite some packages (patched!) that don't do --srcdir builds
> anymore.  etc.  Small things that make `make world' mode hairy.

Fortunately for me, make world is not, and has never been a goal :]. By
this I mean: automated generation of packages and -src packages from a
source tree is a goal, on a per package basis. Generating all the
packages at once will not be feasible once conflicts: is supported and
conflicts exist. The ability to do
for each package
  get-src
  build-bin
  build-src

is desired, but that != make world.

Rob