From: Jakub Narebski <jnareb@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, John 'Warthog9' Hawley <warthog9@kernel.org>,
Drew Northup <drew.northup@maine.edu>, Petr Baudis <pasky@ucw.cz>
Subject: Re: [PATCHv3 2/5] gitweb: Describe CSSMIN and JSMIN in gitweb/INSTALL
Date: Wed, 8 Jun 2011 13:32:18 +0200 [thread overview]
Message-ID: <201106081332.19008.jnareb@gmail.com> (raw)
In-Reply-To: <20110606200126.GB30588@elie>
On Mon, 6 June 2011, Jonathan Nieder wrote:
Thank you very much for your review and comments.
> Jakub Narebski wrote:
>
> > The build-time configuration variables JSMIN and CSSMIN were mentioned
> > only in Makefile; add their description to gitweb/INSTALL.
> >
> > This required moving description of GITWEB_JS up, near GITWEB_CSS and
> > just introduced CSMIN and JSMIN.
>
> Why does this require that? Ah, to make the analogy with GITWEB_CSS
> clear and because the JSMIN description refers to it.
Yes, moving description of GITWEB_JS was required because I wanted to
cover both of CSSMIN and JSMIN with one entry, which entry of course
refers to both GITWEB_CSS and GITWEB_JS.
> > --- a/gitweb/INSTALL
> > +++ b/gitweb/INSTALL
> > @@ -147,6 +147,19 @@ You can specify the following configuration variables when building GIT:
> [...]
> > + * CSSMIN, JSMIN
> > + Invocation of a CSS minifier or a JavaScript minifier, respectively,
> > + working as a filter (source on standard input, minified result on
> > + standard output). If set, it is used to generate a minified version of
> > + 'static/gitweb.css' or 'static/gitweb.js', respectively. *Note* that
> > + minified files would have *.min.css and *.min.js extension, which is
> > + important if you also set GITWEB_CSS and/or GITWEB_JS. [No default]
>
> When I first read this, I thought it meant these command lines were
> going to be cooked into the gitweb script and invoked at run time.
> Maybe (sorry for the rough text):
>
> * CSSMIN, JSMIN
> Command for a CSS minifier or a Javascript minifier, working as a
> filter [...]
> These are used if defined to generate smaller, non human-readable
> versions of 'gitweb/gitweb.css' and 'static/gitweb.js' at
> 'static/gitweb.min.css' and 'static/gitweb.min.js'. Only the minified
> versions are installed, which is important if you also set GITWEB_CSS
> or GITWEB_JS. [No default]
>
> Aside from that, looks good. Thanks.
Thanks. I'll incorporate those comments in next round... or as a separate
improvement (it is not that bad, I think, to not allow it to be fixed
"in tree").
Anyway the description could use some improvements. We need to cover the
following issues:
1. CSSMIN and JSMIN are invoked during building gitweb.
2. CSSMIN and JSMIN are interpreted as shell commands, so
* if you refer to script by full path, you need to quote spaces
yourself, e.g.
JSMIN="'c:/Program Files/JSMin/jsmin.exe'"
* you can provide options, so you can e.g. use
JSMIN="perl -MJavaScript::Minifier=minify -we 'minify(input => *STDIN, output => *STDOUT);'"
3. CSSMIN and JSMIN must accept source on standard input, and print
minified version to standard output, i.e. they are invoked as
$(CSSMIN) <$< >$@
4. Minified files will be named static/gitweb.min.css and
static/gitweb.min.js, respectively
5. If you do not set GITWEB_CSS and GITWEB_JS, but use CSS and/or JSMIN,
they would be set to appropriate values automatically
6. The "install" target in gitweb Makefile, and "install-gitweb" target
in main Makefile, would install minified versions (if any).
7. If you set both CSSMIN and GITWEB_CSS, you have to adjust GITWEB_CSS
by yourself. Same for JSMIN and GITWEB_JS.
Help with wording those would be much appreciated, in more compact form.
Thanks in advance.
--
Jakub Narebski
Poland (not native English speaker)
next prev parent reply other threads:[~2011-06-08 11:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 17:44 [RFC/PATCHv3 0/5] Improving gitweb documentation, creating manpages Jakub Narebski
2011-06-06 17:44 ` [PATCHv3 1/5] gitweb: Move information about installation from README to INSTALL Jakub Narebski
2011-06-06 19:44 ` Jonathan Nieder
2011-06-06 17:44 ` [PATCHv3 2/5] gitweb: Describe CSSMIN and JSMIN in gitweb/INSTALL Jakub Narebski
2011-06-06 20:01 ` Jonathan Nieder
2011-06-08 11:32 ` Jakub Narebski [this message]
2011-06-06 17:44 ` [PATCHv3 3/5] gitweb: Move "Requirements" up " Jakub Narebski
2011-06-06 20:05 ` Jonathan Nieder
2011-06-06 17:44 ` [RFC/PATCHv3 4/5] gitweb: Starting work on a man page for /etc/gitweb.conf (WIP) Jakub Narebski
2011-06-06 22:12 ` Jonathan Nieder
2011-06-06 22:25 ` Jonathan Nieder
2011-06-08 16:40 ` Jakub Narebski
2011-06-07 13:00 ` Drew Northup
2011-06-07 13:44 ` Jonathan Nieder
2011-06-07 16:27 ` Drew Northup
2011-06-07 16:41 ` Jakub Narebski
2011-06-07 17:00 ` Junio C Hamano
2011-06-07 17:43 ` Drew Northup
2011-06-07 19:36 ` Jakub Narebski
2011-06-07 19:50 ` Drew Northup
2011-06-10 17:16 ` Jakub Narebski
2011-06-08 16:35 ` Jakub Narebski
2011-06-06 17:44 ` [RFC/PATCHv3 5/5] 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=201106081332.19008.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=drew.northup@maine.edu \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=pasky@ucw.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).