Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Thu, 29 May 2003 11:28:14 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Lapo Luchini <lapo AT lapo DOT it>
cc: cygwin AT cygwin DOT com
Subject: Re: qmail port successfull
In-Reply-To: <3ED5C5F4.7080208@lapo.it>
Message-ID: <Pine.GSO.4.44.0305291124191.21496-100000@slinky.cs.nyu.edu>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 29 May 2003, Lapo Luchini wrote:

> [snip]
> P.S.: maybe it's just that I'm using FreeBSD more and more, but its
> "ports system" seems to me better each time I think of it (it is a
> collection of some 8000 Makefiles that contains instruction to download
> source form original website, apply patch if necessary, compile and
> install as a system package).
> It is true, of course, that most of the people out there wouln't like to
> compile things, but when it's an automatic non-interactive script, it
> can be a little better maybe.

Hey, why not put the source in the binary package, and have the
postinstall script compile and install the binaries?  Nothing prevents you
from doing that now, AFAICS, and, though a bit weird, it's not much worse
than extracting a tarball (as mingw-runtime does).  Package dependences
will have to be considered carefully, however -- the binary package will
depend on at least gcc and make, perhaps autotools and others...

> This reminds me that maybe it could be cool to have an "install" option
> in "type 2 packages" that installs them directly, without bothering to
> have a "fake" local setup.ini, starting setup, let it install the
> package... this would need some command line "installed package db"
> management of some kind. Or it is already out there, only I didn't
> notice it?

Isn't that what the RPM port eventually hopes to accomplish? ;-)
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/