From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, John 'Warthog9' Hawley <warthog9@kernel.org>,
Petr Baudis <pasky@suse.cz>,
Drew Northup <drew.northup@maine.edu>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [RFC/PATCHv2 1/2] Starting work on a man page for /etc/gitweb.conf (WIP)
Date: Sun, 29 May 2011 22:58:39 +0200 [thread overview]
Message-ID: <201105292258.42845.jnareb@gmail.com> (raw)
In-Reply-To: <7vwrh9nsyr.fsf@alter.siamese.dyndns.org>
On Sun, 29 May 2011, Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>
> > diff --git a/gitweb/Makefile b/gitweb/Makefile
> > index 0a6ac00..582e1b0 100644
> > --- a/gitweb/Makefile
> > +++ b/gitweb/Makefile
> > @@ -112,6 +112,14 @@ endif
> >
> > GITWEB_FILES += static/git-logo.png static/git-favicon.png
> >
> > +GITWEB_MAN5_TXT = gitweb.conf.txt
> > +GITWEB_MAN_TXT = $(GITWEB_MAN1_TXT) $(GITWEB_MAN5_TXT) $(GITWEB_MAN7_TXT)
> > +GITWEB_MAN = $(patsubst %.txt,%.1,$(GITWEB_MAN1_TXT)) \
> > + $(patsubst %.txt,%.5,$(GITWEB_MAN5_TXT)) \
> > + $(patsubst %.txt,%.7,$(GITWEB_MAN7_TXT))
> > +GITWEB_HTML= $(patsubst %.txt,%.html,$(GITWEB_MAN_TXT))
> > +GITWEB_DOC = $(GITWEB_MAN) $(GITWEB_HTML)
> > +
> > GITWEB_REPLACE = \
> > -e 's|++GIT_VERSION++|$(GIT_VERSION)|g' \
> > -e 's|++GIT_BINDIR++|$(bindir)|g' \
> > @@ -155,6 +163,11 @@ test-installed:
> > GITWEB_TEST_INSTALLED='$(DESTDIR_SQ)$(gitwebdir_SQ)' \
> > $(MAKE) -C ../t gitweb-test
> >
> > +### Documentation
> > +
> > +doc:
> > + $(MAKE) -C ../Documentation $(GITWEB_DOC)
> > +
> > ### Installation rules
> >
> > install: all
>
> I am not sure if this target is needed or even desirable.
Well, this is the target that it is nice to have. The implementation
needs to be improved, as you noticed.
> The only potential benefit this complexity and risk of these build
> procedure knowledge diverge what is in ../Documentation is to let you say
> "cd gitweb && make doc" and avoid building the rest of the documentation,
> but I personally do not find it necessary at all.
>
> Aren't you making a mistake similar to the one that let instaweb have
> intimate and unnecessary knowledge of how to build gitweb, which you
> recently cleaned up?
Thanks for sanity check!
Instead of duplicating Documentation/Makefile knowledge in gitweb/Makefile,
let's just proxy to Documentation/Makefile like for 'test' target:
+doc:
+ $(MAKE) -C ../Documentation gitweb
+
In Documentation/Makefile the new 'gitweb' target could look just like
this:
+GITWEB_DOC = $(filter gitweb.%,$(DOC_HTML) $(DOC_MAN1) $(DOC_MAN5) $(DOC_MAN7))
+gitweb: $(GITWEB_DOC)
And it would be much shorter, too.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2011-05-29 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 19:50 [RFC/PATCHv2 0/2] Starting work on man pages for gitweb and gitweb.conf (WIP) Jakub Narebski
2011-05-29 19:50 ` [RFC/PATCHv2 1/2] Starting work on a man page for /etc/gitweb.conf (WIP) Jakub Narebski
2011-05-29 20:37 ` Junio C Hamano
2011-05-29 20:58 ` Jakub Narebski [this message]
2011-05-29 19:50 ` [RFC/PATCHv2 2/2] gitweb: Starting work on a man page for gitweb (WIP) Jakub Narebski
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=201105292258.42845.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=drew.northup@maine.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=pasky@suse.cz \
--cc=warthog9@kernel.org \
/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).