X-Spam-Check-By: sourceware.org Date: Mon, 18 Jun 2007 16:47:46 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: emacs 22.1? Message-ID: <20070618204746.GA1813@ednor> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20070618084646.GK4179@calimero.vinschen.de> <20070618130035.GN4179@calimero.vinschen.de> <1182194212.467427@alpaka.in-berlin.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1182194212.467427@alpaka.in-berlin.de> User-Agent: Mutt/1.5.15 (2007-04-06) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Mon, Jun 18, 2007 at 09:16:50PM +0200, Steffen Sledz wrote: >Corinna Vinschen schrieb: >>The latest is the emacs source package you get when choosing to >>download the package source with setup.exe. Other than that, have a >>close look into http://cygwin.com/setup.html > >OK, I've done this. But i miss some information for a newbie like me >(e.g. What is the best way to setup an environment for building the >packages? What toolchain to use? ...?). May be there is a maintainer >tutorial and/or FAQ? Or something like a mentoring program for new >maintainers? 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. cgf -- 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/