X-Spam-Check-By: sourceware.org
X-Envelope-From: sledz AT zone42 DOT org
X-Envelope-To: <cygwin AT cygwin DOT com>
Date: Tue, 19 Jun 2007 08:35:34 +0200 (CEST)
From: Steffen Sledz <sledz AT zone42 DOT org>
Reply-To: Steffen Sledz <sledz AT zone42 DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: emacs 22.1?
In-Reply-To: <20070618204746.GA1813@ednor>
Message-ID: <Pine.LNX.4.64.0706190816340.16813@recycler.in-berlin.de>
References: <Pine DOT LNX DOT 4 DOT 64 DOT 0706181035280 DOT 5368 AT recycler DOT in-berlin DOT de>  <20070618084646 DOT GK4179 AT calimero DOT vinschen DOT de> <Pine DOT LNX DOT 4 DOT 64 DOT 0706181447040 DOT 5368 AT recycler DOT in-berlin DOT de>  <20070618130035 DOT GN4179 AT calimero DOT vinschen DOT de> <1182194212 DOT 467427 AT alpaka DOT in-berlin DOT de>  <20070618204746 DOT GA1813 AT ednor>
X-Privacy: Ich widerspreche der Nutzung o. Weitergabe meiner Daten fuer die Markt-/Meinungsforschung und/oder fuer Werbezwecke gemaesz Par.28.3 BDSG
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score:  (-1.799) ALL_TRUSTED,BAYES_50
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

Hello Christopher,

On Mon, 18 Jun 2007, Christopher Faylor wrote:
> This is one of those situations where a certain amount of core 
> competence is required.  If you are not really familiar with the concept 
> of building packages (especially a package as presumably large and 
> complicated as emacs) you might want to think twice about what you're 
> volunteering to do.  How can you possibly maintain and support a package 
> if you don't have any idea about how to build it?  How are you going to 
> deal with bug reports?
> 
> I'm *really* not trying to be mean here.  I'm just trying to make sure 
> that you understand what you're getting into.

thanx for your warning. It is clear to me that this is not an easy job and 
i'm not sure now to do this work. I'm just doing some examinations about 
the amount of work waiting for me. ;-)

But i believe i've a good core competence. I'm a software developer and 
familiar with building packages for other distributions (e.g. RPM or 
fli4l). I've also studied the mentioned http://cygwin.com/setup.html. But 
there are some open distribution specific questions:

Is there a suggested build environment (may be a prepared VMware image)? 
Or just installing cygwin base and devel?

What about file ownership and permissions? Under which user account (uid) 
the packages should be build?

How to mark obsolete packages? In emacs 22.1 leim is integrated. So the 
extra leim package is obsolete.

The old emacs package is neither build using method One nor method Two 
mentioned on http://cygwin.com/setup.html. Is there something to pay 
attention to in the new package to avoid update problems?

May be some more...

Regards,
Steffen


--
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/