public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@zone42.org>
To: cygwin-apps@cygwin.com
Subject: Re: Maintainer newbie questions
Date: Sun, 08 Jul 2007 08:43:00 -0000	[thread overview]
Message-ID: <4690A39C.7070201@zone42.org> (raw)
In-Reply-To: <468AB0A1.8D9CB133@dessent.net>

Brian Dessent schrieb:
>> 3. Same question for the build requirements.
> 
> There's no automatic way to determine this, you just have to know which
> developer tools are required to build the software.  For the most part it's
> pretty straightforward, e.g. it requires the 'make' package if a step was typing
> make, and if there's C code you require 'gcc' (which automatically pulls in
> binutils and w32api, so you don't really need to mention those, but some people
> still do.)  You also need to list the corresponding -devel packages of any
> libraries that your package links to, which you determined above.  If you're
> using cygport then that favors running autoreconf at configure time instead of
> running it on the builder's machine and including changes to generated files in
> the patch, so you'd want to list autoconf/automake/libtool/m4 as build
> requirements if you use cygport.

What's the policy for the build requirements in the README files, if
packages are build from the same source package? Same list in all of
them? Just a referenve to the main package?

Steffen

      reply	other threads:[~2007-07-08  8:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03 17:38 Steffen Sledz
2007-07-03 20:25 ` Brian Dessent
2007-07-08  8:43   ` Steffen Sledz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4690A39C.7070201@zone42.org \
    --to=sledz@zone42.org \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).