Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com To: "Robert Collins" Cc: "Charles Wilson" , Subject: Re: broken setup.hint files References: <3C126412 DOT 1060903 AT ece DOT gatech DOT edu> <3C1283D0 DOT 3090201 AT ece DOT gatech DOT edu> <3C12F5CD DOT 9030400 AT ece DOT gatech DOT edu> <00ae01c18153$b4dbfff0$0200a8c0 AT lifelesswks> Organization: Jan at Appel From: Jan Nieuwenhuizen Date: 10 Dec 2001 09:42:25 +0100 In-Reply-To: <00ae01c18153$b4dbfff0$0200a8c0@lifelesswks> ("Robert Collins"'s message of "Mon, 10 Dec 2001 19:21:44 +1100") Message-ID: Lines: 25 User-Agent: Gnus/5.090003 (Oort Gnus v0.03) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii "Robert Collins" writes: > I don't grok this. Take conflicting packages - they do exist - how do > you propose to make world on them? Oh, I didn't introduce the term make world here, but I liked it and thus copied it. [as everyone probably knew by then I was doing cross-builds including packaging, a *bsd make world is not exactly what I do.] What I mean is: all packages should be automagically buildable: fetch, unpack, build, repack. The 'make world' aspect: do that for all packages available, is something that will follow as soon as all packages behave. > I maintain that the ability to automatically make a package from the > commandline is desired, but that that and make world are orthogonal. Ok, just a matter of definition, so it seems. Jan. -- Jan Nieuwenhuizen | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org