From: Fabio Massimo Di Nitto <fabbione@ubuntu.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [RFC/PATCH] Collecting common Makefile snippets
Date: Mon, 27 Aug 2007 09:19:58 +0200 [thread overview]
Message-ID: <46D27B1E.90300@ubuntu.com> (raw)
The patch in attachment is just a working example.
The general idea is to start to collect all common Makefile targets into
their own makefile snippets now that most of the Makefiles share lots of common
targets.
Pro:
- It will allow us to change common bits in one place and they will be
automatically propagated all over the tree instead of having to change N Makefiles.
- General Makefiles will be much smaller.
- It will still be possible to special case bits here and there. (from this
example patch you can look at gfs/Makefile and fence/agents/Makefile that are
not touched by the patch).
- It will be possible to override targets in local Makefiles.
Cons:
- When creating new makefiles you need to know which snippets to include.
- When reading a makefile you need to remember what targets are automatically
sourced from a snippet.
Cheers
Fabio
--
I'm going to make him an offer he can't refuse.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: collect.diff
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20070827/b9f3fd10/attachment.ksh>
reply other threads:[~2007-08-27 7:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46D27B1E.90300@ubuntu.com \
--to=fabbione@ubuntu.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 NNTP newsgroup(s).