From: Jakub Narebski <jnareb@gmail.com>
To: Mark Rada <marada@uwaterloo.ca>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Charles Bailey <charles@hashpling.org>
Subject: Re: [PATCH] gitweb: simplify gitweb.min.* generation and clean-up rules
Date: Thu, 15 Apr 2010 08:11:53 +0200 [thread overview]
Message-ID: <201004150811.55627.jnareb@gmail.com> (raw)
In-Reply-To: <4BC689FF.9080308@mailservices.uwaterloo.ca>
Mark Rada wrote:
> GITWEB_CSS and GITWEB_JS are meant to be "what URI should the installed
> cgi script use to refer to the stylesheet and JavaScript", never "this
> is the name of the file we are building".
>
> Lose incorrect assignment to them.
>
> While we are at it, lose FILES that is used only for "clean" target in a
> misguided way. "make clean" should try to remove all the potential
> build artifacts regardless of a minor configuration change. Instead of
> trying to remove only the build product "make clean" would have created
> if it were run without "clean", explicitly list the three potential build
> products for removal.
>
> In addition, this patch tries to make sure that the scripts are
> regenerated whenever the replacement variables are modified. For a good
> measure, if you used different JSMIN/CSSMIN since the last time you
> produced minified version of these files, they are regenerated.
>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> Tested-by: Mark Rada <marada@uwaterloo.ca>
>
>
> ---
>
> I gave this a test run:
> With just jsmin enabled
> With just cssmin enabled
> With neither enabled
> With both enabled
> Overriding GITWEB_JS
> Overriding GITWEB_JS and jsmin enabled
Thank you very much.
> Instaweb will still generate what it needs to the first time around,
> but if you change GITWEB_JS or the JSMIN (or css equivalents) then you
> have to regenerate gitweb first manually before instaweb. I'm not sure
> if it would be best to swallow up instaweb into this same patch or to
> fix it separately (also, I still don't quite understand how this patch
> works).
Instaweb would need to check if gitweb was run with its GITWEB_JS and
with curent JSMIN... and this should be I think a separate patch.
> config.mak.in | 2 +
> gitweb/Makefile | 75 ++++++++++++++++++++++++++++---------------------------
> 2 files changed, 40 insertions(+), 37 deletions(-)
>
> diff --git a/config.mak.in b/config.mak.in
> index 6008ac9..bb828fe 100644
> --- a/config.mak.in
> +++ b/config.mak.in
> @@ -57,3 +57,5 @@ FREAD_READS_DIRECTORIES=@FREAD_READS_DIRECTORIES@
> SNPRINTF_RETURNS_BOGUS=@SNPRINTF_RETURNS_BOGUS@
> NO_PTHREADS=@NO_PTHREADS@
> PTHREAD_LIBS=@PTHREAD_LIBS@
> +GITWEB_JS=/home/ferrous/gitweb.js
> +
I think that you have committed this by accident...
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2010-04-15 6:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 3:37 [PATCH] gitweb: simplify gitweb.min.* generation and clean-up rules Mark Rada
2010-04-15 4:11 ` Mark Rada
2010-04-15 6:11 ` Jakub Narebski [this message]
2010-04-15 12:57 ` [PATCHv2] " Mark Rada
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=201004150811.55627.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=charles@hashpling.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=marada@uwaterloo.ca \
/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).