Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <41658037.8B0CA567@dessent.net> Date: Thu, 07 Oct 2004 10:43:19 -0700 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: qmail, DJB licensing References: <41655E51 DOT 4040005 AT x-ray DOT at> <20041007152254 DOT GL7398 AT trixie DOT casa DOT cgf DOT cx> <4165702C DOT 2080506 AT x-ray DOT at> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Reini Urban wrote: > So we could follow Igor's suggestion providing the sources in the binary > package and compile it after download. > http://www.cygwin.com/ml/cygwin/2003-05/msg01654.html > At least better than nothing. exim would need a comparative and simplier > MTA. > > I failed with trying to do some heavy processing with my new postgresql > postinstall script. The compile step in a postinstall script would need > to open a seperate console detached from setup.exe probably. Otherwise I > see no light. I don't see why you're interested in making an extremely unwieldy pseudo-binary package for this. It just seems like a nightmare to support for both packagers and users, all because DJB won't let you distribute anything but pristine sources. Does maildir even work without resorting to managed mounts? Have you considered that too? It sounds like even if it were possible to package qmail there would be many hurdles that would cause it to be hardly a "drop-in" package. Brian -- 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/