public inbox for
 help / color / mirror / Atom feed
From: Gary Benson <>
Subject: Fluorine
Date: Fri, 14 Nov 2003 15:48:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> wrote:
> Log message:
> 	Initial revision (good enough for commons-logging)

This is something I've been working on these past couple of days.  I
just got fed up of the complete pain in the arse that maintaining RHUG
packages is: it's just too easy to lose resources from libraries or
jars, get confused over $(srcdir) != $(builddir), link the libraries
incorrectly so they don't dlopen(), etc, etc.  So I'm writing a
templater to generate the awkward files, starting with and, but later to include the spec and rml files too.  The
input files to the templater are tiny -- ant's one is less than a
screenful.  Attached is commons-logging's one, if you want to see what
they look like.

And yes, I'm aware of the irony of writing something to generate files
for other programs that generate files :)


       reply	other threads:[~2003-11-14 15:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2003-11-14 15:48 ` Gary Benson [this message]
2003-11-14 15:56   ` Fluorine Gary Benson

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