From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] DOCS= target in Makefile
Date: Tue, 1 Jul 2008 10:18:09 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0807011013520.27368@trider-g7> (raw)
Hi guys,
i just pushed the changes to master that allows you to define a DOCS=
keyword at the top of your Makefile and specify files that will be
installed in docdir (default = /usr/share/doc/cluster).
Please make sure to spread it around where needed.
Also, the target dir is shared. If 2 Makefiles install a generic README,
the latter wins. So be sensible and careful.
I suggest, that for example, if you ship some generic named piece of
documentation, add a very small and simple README.$foo file that explains
what the other files are.
Example:
config/pluging/ldap install to .ldif files.
Add README.ldap to explain what those 2 files are and how they can be
used.
Thanks
Fabio
--
I'm going to make him an offer he can't refuse.
reply other threads:[~2008-07-01 8:18 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=Pine.LNX.4.64.0807011013520.27368@trider-g7 \
--to=fdinitto@redhat.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).