From: Junio C Hamano <junkio@cox.net>
To: Eygene Ryabinkin <rea-git@codelabs.ru>
Cc: Jakub Narebski <jnareb@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: [PATCH] Add --with-tcltk and --without-tcltk to configure.
Date: Wed, 28 Mar 2007 12:48:45 -0700 [thread overview]
Message-ID: <7vps6tf8te.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20070328091209.GQ14837@codelabs.ru
Eygene Ryabinkin <rea-git@codelabs.ru> writes:
> --with-tcltk enables the search of the Tcl/Tk interpreter. If no
> interpreter is found then Tcl/Tk dependend parts are disabled.
>
> --without-tcltk unconditionally disables Tcl/Tk dependent parts.
>
> The original behaviour is not changed: bare './configure' just
> installs the Tcl/Tk part doing no checks for the interpreter.
>
> Makefile knob named NO_TCLTK was introduced. It prevents the build
> and installation of the Tcl/Tk dependent parts.
>
> Signed-off-by: Eygene Ryabinkin <rea-git@codelabs.ru>
> ---
Thanks.
Is this supposed to be the first in the series? I thought you
said you were going to do NO_TCLTK without anything else at all
first, and then TCLTK_PATH patch. I am a bit lost here.
> +# Define NO_TCLTK if you do not want Tcl/Tk GUI.
> +#
> +# The TCLTK_PATH variable governs the location of the Tck/Tk interpreter.
> +# If not set it defaults to the bare 'wish'. If it is set to the empty
> +# string then NO_TCLTK will be forced (this is used by configure script).
> +#
Grumble. If you are doing this, then there is not much point to
have two separate patches, is it?
> @@ -684,7 +696,9 @@ ifneq (,$X)
> endif
>
> all::
> +ifndef NO_TCLTK
> $(QUIET_SUBDIR0)git-gui $(QUIET_SUBDIR1) all
> +endif
> $(QUIET_SUBDIR0)perl $(QUIET_SUBDIR1) PERL_PATH='$(PERL_PATH_SQ)' prefix='$(prefix_SQ)' all
> $(QUIET_SUBDIR0)templates $(QUIET_SUBDIR1)
Although you were not supposed to be talking about paths, since
you've already introduced TCLTK_PATH, it should be passed down
to git-gui here, I think.
> @@ -955,11 +974,17 @@ dist: git.spec git-archive
> @mkdir -p $(GIT_TARNAME)
> @cp git.spec $(GIT_TARNAME)
> @echo $(GIT_VERSION) > $(GIT_TARNAME)/version
> +ifndef NO_TCLTK
> @$(MAKE) -C git-gui TARDIR=../$(GIT_TARNAME)/git-gui dist-version
> $(TAR) rf $(GIT_TARNAME).tar \
> $(GIT_TARNAME)/git.spec \
> $(GIT_TARNAME)/version \
> $(GIT_TARNAME)/git-gui/version
> +else
> + $(TAR) rf $(GIT_TARNAME).tar \
> + $(GIT_TARNAME)/git.spec \
> + $(GIT_TARNAME)/version
> +endif
> @rm -rf $(GIT_TARNAME)
> gzip -f -9 $(GIT_TARNAME).tar
>
Why should a source distribution exclude git-gui/ directory? I
think it is sensible to ship a source that contains all. You
are shipping gitk even without NO_TCLTK anyway, too.
And from the part 2:
> @@ -705,6 +709,12 @@ endif
> strip: $(PROGRAMS) git$X
> $(STRIP) $(STRIP_OPTS) $(PROGRAMS) git$X
>
> +gitk-wish: gitk GIT-GUI-VARS
> + $(QUIET_GEN)rm -f $@ $@+ && \
> + sed -e'1,3s|^exec .* "$$0"|exec $(subst |,'\|',$(TCLTK_PATH_SQ)) "$$0"|' < gitk > $@+ && \
> + chmod +x $@+ && \
> + mv -f $@+ $@
> +
This subst() is a nice attention to the detail. I like it,
although in practice I do not think anybody is insane enough to
have a pipe character in the directory name that leads to wish.
I separated your two patches into three with minor modifications
and parked them in 'pu'. We need to arrange with Shawn when to
apply the git-gui/ parts of the patch to his tree, but we are
not in a rush.
next prev parent reply other threads:[~2007-03-28 19:48 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 11:45 [PATCH] Added make options NO_GUI and WITH_P4IMPORT Eygene Ryabinkin
2007-03-21 0:35 ` Jakub Narebski
2007-03-21 5:14 ` Eygene Ryabinkin
2007-03-21 11:16 ` Johannes Schindelin
2007-03-21 11:50 ` Eygene Ryabinkin
2007-03-21 14:25 ` Johannes Schindelin
2007-03-21 14:38 ` Paolo Bonzini
2007-03-21 14:42 ` Eygene Ryabinkin
2007-03-21 14:49 ` Paolo Bonzini
2007-03-21 14:58 ` Alex Riesen
2007-03-24 23:16 ` Jakub Narebski
2007-03-21 14:40 ` Eygene Ryabinkin
2007-03-21 15:35 ` Johannes Schindelin
2007-03-21 16:01 ` Eygene Ryabinkin
2007-03-21 16:17 ` Junio C Hamano
2007-03-26 7:31 ` Eygene Ryabinkin
2007-03-26 7:32 ` [PATCH] Added options NO_TCLTK, WITH_P4IMPORT and --with-tcltk/--without-tcltk Eygene Ryabinkin
2007-03-26 8:27 ` Junio C Hamano
2007-03-27 10:26 ` [PATCH] Add the WITH_P4IMPORT knob to the Makefile Eygene Ryabinkin
2007-03-27 10:54 ` Junio C Hamano
2007-03-27 11:22 ` Eygene Ryabinkin
2007-03-27 11:25 ` [PATCH] Added git-p4 package to the list of git RPMs Eygene Ryabinkin
2007-03-27 16:03 ` [PATCH] Remove unused WITH_OWN_SUBPROCESS_PY from RPM spec Brian Gernhardt
2007-04-04 18:30 ` [PATCH] Added git-p4 package to the list of git RPMs Junio C Hamano
2007-04-05 12:50 ` Eygene Ryabinkin
2007-03-26 8:30 ` [PATCH] Added options NO_TCLTK, WITH_P4IMPORT and --with-tcltk/--without-tcltk Jakub Narebski
2007-03-26 8:36 ` Junio C Hamano
2007-03-26 10:03 ` Eygene Ryabinkin
2007-03-27 4:12 ` Junio C Hamano
2007-03-27 6:59 ` Eygene Ryabinkin
2007-03-27 10:24 ` [PATCH] Added configure options --with-tcltk/--without-tcltk Eygene Ryabinkin
2007-03-27 10:53 ` Junio C Hamano
2007-03-27 11:07 ` Eygene Ryabinkin
2007-03-28 1:52 ` Junio C Hamano
2007-03-28 9:12 ` [PATCH] Add --with-tcltk and --without-tcltk to configure Eygene Ryabinkin
2007-03-28 9:13 ` [PATCH] Added Tcl/Tk interpreter path rewriting for the GUI tools Eygene Ryabinkin
2007-03-28 19:48 ` Junio C Hamano [this message]
2007-03-29 7:44 ` [PATCH] Add --with-tcltk and --without-tcltk to configure Eygene Ryabinkin
2007-03-29 8:00 ` Junio C Hamano
2007-03-29 8:29 ` Eygene Ryabinkin
2007-03-29 8:35 ` Junio C Hamano
2007-03-29 8:58 ` Eygene Ryabinkin
2007-03-29 9:12 ` Tom Prince
2007-03-29 10:06 ` Eygene Ryabinkin
2007-03-29 10:06 ` [PATCH] Eliminate checks of user-specified Tcl/Tk interpreter Eygene Ryabinkin
2007-03-29 10:07 ` [PATCH] Added correct Python path to the RPM specfile Eygene Ryabinkin
2007-03-26 8:25 ` [PATCH] Added make options NO_GUI and WITH_P4IMPORT Junio C Hamano
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=7vps6tf8te.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=rea-git@codelabs.ru \
/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).