public inbox for
 help / color / mirror / Atom feed
From: Chad Walstrom <>
Subject: Re: My experiences building GNATS 4.1.0
Date: Thu, 24 Mar 2005 09:07:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1.1: Type: text/plain, Size: 910 bytes --]

By the way, it isn't GNATS 4.10.  You're about 9 releases in the future.

On Wed, Mar 23, 2005 at 10:21:44AM +0200, Mike M. Volokhov wrote:
> Another question is why build process so unclean (missing .c files,
> missing variables, some "magic" explicit rules at the end of makefile,
> and so on)?

Historical remnants.

> IMHO we should cleanup makefiles to be compliant to generic make rules
> or use GNU atomake framework (but I'm personally are not familiar with
> GNU build tools). Which way more preferred?

I would like to see a migration to automake and a single
file.  However, I didn't want to hold up rolling out 4.1.0 any longer
than necessary.  Now that we've reached that milestone, we can look into
cleaning it up a bit more.

Chad Walstrom <> 
           assert(expired(knowledge)); /* core dump */

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

Help-gnats mailing list

  parent reply	other threads:[~2005-03-23 17:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-06 21:07 GNATS 4.1.0 Released! Chad Walstrom
2005-03-07 17:35 ` David S Gathright
2005-03-07 18:10   ` 'Chad Walstrom'
2005-03-08 15:42     ` 'Chad Walstrom'
2005-03-08  2:44   ` David S Gathright
2005-03-23  8:35 ` My experiences building GNATS 4.10 Tim Buck
2005-03-23 13:37   ` Mike M. Volokhov
2005-03-23 15:33     ` Tim Buck
2005-03-24  9:07     ` Chad Walstrom [this message]
2005-03-28 16:59       ` My experiences building GNATS 4.1.0 Mike M. Volokhov

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:

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

  git send-email \ \ \ \

* 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).