Date: Sat, 21 Jan 2012 13:23:51 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: what happened to [PATCH] setup -e, --separate-src-dirs option (http://sourceware.org/ml/cygwin-apps/2011-12/msg00022.html)
Message-ID: <20120121182351.GB26978@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <jf4fa6$ml0$1 AT dough DOT gmane DOT org> <jfen3e$tkk$1 AT dough DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <jfen3e$tkk$1@dough.gmane.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Sat, Jan 21, 2012 at 07:54:04AM -0800, Hans Horn wrote:
>On 1/17/2012 10:39 AM, Hans Horn wrote:
>> As subject line says.
>> As far as I recall, this got a lot of +1 votes.
>
>Nothing? Not even an insult? That's disappointing

Not an insult but if you were reading the thread you saw that I had a
problem with the approach.  I'd rather not burden setup.exe with unneeded
code when the problem could be handled either by the package maintainer
or by changing the way files are uploaded to sourceware.

I started working on a new mechanism for uploading packages to
sourceware.  It requires uploading a new package to a staging area where
a validity check (and maybe package massaging) is done before a package
is moved to the release area.  But, I was bogged down by home computer
problems and haven't finished it yet.  I will get to it in the next
month or so, however.

cgf

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