{"thread":{"id":"8580","subject":"[PATCH] Introduce file with the common default build-time items.","startedAt":"2007-06-13T05:43:16Z","lastAt":"2007-06-15T10:28:48Z","messageCount":11,"participants":["Eygene Ryabinkin","Shawn O. Pearce","Johannes Sixt"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"44890","messageId":"20070613054316.GN86872@void.codelabs.ru","threadId":"8580","inReplyTo":null,"subject":"[PATCH] Introduce file with the common default build-time items.","fromName":"Eygene Ryabinkin","fromEmail":"rea-git@codelabs.ru","sentAt":"2007-06-13T05:43:16Z","receivedAt":"2007-06-13T05:43:16Z","isPatch":true,"sender":{"key":"rea-git@codelabs.ru","avatar":null},"body":"Words 'wish' and 'tclsh' are scattered across at least three files,\nbut they are tied to the same entities. To ease the maintenance\nand remove errors, these configuration items were gathered into the\nseparate file named 'common-make-vars.def'.\n\nSigned-off-by: Eygene Ryabinkin \n---\n Makefile | 17 +++++++++++------\n common-make-vars.def | 11 +++++++++++\n configure.ac | 4 +++-\n git-gui/Makefile | 6 ++++--\n 4 files changed, 29 insertions(+), 9 deletions(-)\n create mode 100644 common-make-vars.def\n\ndiff --git a/Makefile b/Makefile\nindex 6cd9ea2..e98f16b 100644\n--- a/Makefile\n+++ b/Makefile\n@@ -116,16 +116,21 @@ all::\n #\n # The TCL_PATH variable governs the location of the Tcl interpreter\n # used to optimize git-gui for your system. Only used if NO_TCLTK\n-# is not set. Defaults to the bare 'tclsh'.\n+# is not set. Defaults to the value of the __GIT_DEFAULT_TCLSH_NAME\n+# from common-make-vars.def.\n #\n-# The TCLTK_PATH variable governs the location of the Tcl/Tk interpreter.\n-# If not set it defaults to the bare 'wish'. If it is set to the empty\n-# string then NO_TCLTK will be forced (this is used by configure script).\n+# The TCLTK_PATH variable governs the location of the Tcl/Tk\n+# interpreter. If not set it defaults to the value of the\n+# __GIT_DEFAULT_TCLTK_NAME from common-make-vars.def. If it is set\n+# to the empty string then NO_TCLTK will be forced (this is used\n+# by configure script).\n #\n \n GIT-VERSION-FILE: .FORCE-GIT-VERSION-FILE\n \t@$(SHELL_PATH) ./GIT-VERSION-GEN\n -include GIT-VERSION-FILE\n+# Default values\n+-include common-make-vars.def\n \n uname_S := $(shell sh -c 'uname -s 2>/dev/null || echo not')\n uname_M := $(shell sh -c 'uname -m 2>/dev/null || echo not')\n@@ -177,8 +182,8 @@ AR ?= ar\n TAR ?= tar\n INSTALL ?= install\n RPMBUILD ?= rpmbuild\n-TCL_PATH ?= tclsh\n-TCLTK_PATH ?= wish\n+TCL_PATH ?= $(__GIT_DEFAULT_TCLSH_NAME)\n+TCLTK_PATH ?= $(__GIT_DEFAULT_TCLTK_NAME)\n \n export TCL_PATH TCLTK_PATH\n \ndiff --git a/common-make-vars.def b/common-make-vars.def\nnew file mode 100644\nindex 0000000..43a3a8b\n--- /dev/null\n+++ b/common-make-vars.def\n@@ -0,0 +1,11 @@\n+# This file is meant to be sourced from the autoconf script\n+# and included from the Makefile. It carries the default values\n+# to eliminate their redundancy across the files. The syntax\n+# is 'name=value' without extra spaces across the '=' sign to\n+# make shell happy. Symbols '#' are starting comments ;))\n+\n+# Default Tcl/Tk interpreter name\n+__GIT_DEFAULT_TCLTK_NAME=wish\n+\n+# Default Tcl interpreter name\n+__GIT_DEFAULT_TCLSH_NAME=tclsh\ndiff --git a/configure.ac b/configure.ac\nindex 50d2b85..fd1d241 100644\n--- a/configure.ac\n+++ b/configure.ac\n@@ -12,6 +12,8 @@ config_in=config.mak.in\n \n echo \"# ${config_append}. Generated by configure.\" > \"${config_append}\"\n \n+## Defaults\n+source common-make-vars.def\n \n ## Definitions of macros\n # GIT_CONF_APPEND_LINE(LINE)\n@@ -97,7 +99,7 @@ AC_CHECK_PROGS(TAR, [gtar tar])\n if test -z \"$NO_TCLTK\"; then\n if test \"$with_tcltk\" = \"\"; then\n # No Tcl/Tk switches given. Do not check for Tcl/Tk, use bare 'wish'.\n- TCLTK_PATH=wish\n+ TCLTK_PATH=${__GIT_DEFAULT_TCLTK_NAME}\n AC_SUBST(TCLTK_PATH)\n elif test \"$with_tcltk\" = \"yes\"; then\n # Tcl/Tk check requested.\ndiff --git a/git-gui/Makefile b/git-gui/Makefile\nindex 3de0de1..654641a 100644\n--- a/git-gui/Makefile\n+++ b/git-gui/Makefile\n@@ -6,6 +6,8 @@ all::\n GIT-VERSION-FILE: .FORCE-GIT-VERSION-FILE\n \t@$(SHELL_PATH) ./GIT-VERSION-GEN\n -include GIT-VERSION-FILE\n+# Default values\n+-include ../common-make-vars.def\n \n SCRIPT_SH = git-gui.sh\n GITGUI_BUILT_INS = git-citool\n@@ -36,8 +38,8 @@ ifndef V\n \tQUIET_2DEVNULL = 2>/dev/null\n endif\n \n-TCL_PATH ?= tclsh\n-TCLTK_PATH ?= wish\n+TCL_PATH ?= $(__GIT_DEFAULT_TCLSH_NAME)\n+TCLTK_PATH ?= $(__GIT_DEFAULT_TCLTK_NAME}\n \n ifeq ($(findstring $(MAKEFLAGS),s),s)\n QUIET_GEN =\n-- \n1.5.2.1\n"},{"id":"45036","messageId":"20070614043633.GV6073@spearce.org","threadId":"8580","inReplyTo":"20070613054316.GN86872@void.codelabs.ru","subject":"Re: [PATCH] Introduce file with the common default build-time items.","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-06-14T04:36:33Z","receivedAt":"2007-06-14T04:36:33Z","isPatch":true,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Eygene Ryabinkin wrote:\n> Words 'wish' and 'tclsh' are scattered across at least three files,\n> but they are tied to the same entities. To ease the maintenance\n> and remove errors, these configuration items were gathered into the\n> separate file named 'common-make-vars.def'.\n...\n> diff --git a/git-gui/Makefile b/git-gui/Makefile\n> index 3de0de1..654641a 100644\n> --- a/git-gui/Makefile\n> +++ b/git-gui/Makefile\n> @@ -6,6 +6,8 @@ all::\n> GIT-VERSION-FILE: .FORCE-GIT-VERSION-FILE\n> \t@$(SHELL_PATH) ./GIT-VERSION-GEN\n> -include GIT-VERSION-FILE\n> +# Default values\n> +-include ../common-make-vars.def\n\nA good idea to try and make these all common, but you cannot do this,\nor at least this part of the patch.\n\nThe git-gui subdirectory of git.git is actually its own project,\nmaintained in its own Git repository. It appears inside of\ngit.git only as a convience for users. So I cannot reference\n../common-make-vars.def as not all git-gui repositories have a\ngit.git repository wrapped around them.\n\n-- \nShawn.\n"},{"id":"45057","messageId":"20070614095654.GT86872@void.codelabs.ru","threadId":"8580","inReplyTo":"20070614043633.GV6073@spearce.org","subject":"Re: [PATCH] Introduce file with the common default build-time items.","fromName":"Eygene Ryabinkin","fromEmail":"rea-git@codelabs.ru","sentAt":"2007-06-14T09:56:54Z","receivedAt":"2007-06-14T09:56:54Z","isPatch":true,"sender":{"key":"rea-git@codelabs.ru","avatar":null},"body":"Shawn, good day.\n\nThu, Jun 14, 2007 at 12:36:33AM -0400, Shawn O. Pearce wrote:\n> Eygene Ryabinkin wrote:\n> > Words 'wish' and 'tclsh' are scattered across at least three files,\n> > but they are tied to the same entities. To ease the maintenance\n> > and remove errors, these configuration items were gathered into the\n> > separate file named 'common-make-vars.def'.\n> ...\n> > diff --git a/git-gui/Makefile b/git-gui/Makefile\n> > index 3de0de1..654641a 100644\n> > --- a/git-gui/Makefile\n> > +++ b/git-gui/Makefile\n> > @@ -6,6 +6,8 @@ all::\n> > GIT-VERSION-FILE: .FORCE-GIT-VERSION-FILE\n> > \t@$(SHELL_PATH) ./GIT-VERSION-GEN\n> > -include GIT-VERSION-FILE\n> > +# Default values\n> > +-include ../common-make-vars.def\n> \n> A good idea to try and make these all common, but you cannot do this,\n> or at least this part of the patch.\n> \n> The git-gui subdirectory of git.git is actually its own project,\n> maintained in its own Git repository.\n\nOK, but then may be it will be logical to put Tcl/Tk-related variables\nto the git-gui/common-make-vars.def? I am a little worried about\nthis, because gitk is the part of the git.git and it should get the\nvariables too. The drawback here is if you will update your git-gui\nrepo, then git.git will need to wait for your import to get the\nchanges in the variables. And this will seriously couple git.git\nand git-gui, though I don't know if it is good or bad.\n\nAny ideas?\n-- \nEygene\n"},{"id":"45075","messageId":"20070614150929.GA18491@spearce.org","threadId":"8580","inReplyTo":"20070614095654.GT86872@void.codelabs.ru","subject":"Re: [PATCH] Introduce file with the common default build-time items.","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-06-14T15:09:29Z","receivedAt":"2007-06-14T15:09:29Z","isPatch":true,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Eygene Ryabinkin wrote:\n> \n> Thu, Jun 14, 2007 at 12:36:33AM -0400, Shawn O. Pearce wrote:\n> > Eygene Ryabinkin wrote:\n> > > Words 'wish' and 'tclsh' are scattered across at least three files,\n> > > but they are tied to the same entities. To ease the maintenance\n> > > and remove errors, these configuration items were gathered into the\n> > > separate file named 'common-make-vars.def'.\n...\n> > A good idea to try and make these all common, but you cannot do this,\n> > or at least this part of the patch.\n> \n> OK, but then may be it will be logical to put Tcl/Tk-related variables\n> to the git-gui/common-make-vars.def? I am a little worried about\n> this, because gitk is the part of the git.git and it should get the\n> variables too. The drawback here is if you will update your git-gui\n> repo, then git.git will need to wait for your import to get the\n> changes in the variables. And this will seriously couple git.git\n> and git-gui, though I don't know if it is good or bad.\n\nNo, because Junio has already stated a desire to remove git-gui.git\nfrom git.git and convert it to a proper subproject by the time of\nGit 1.6. That means the git-gui/ subdirectory will become optional,\nthough I imagine most git-gui users will still have it. But not\nall Git users are git-gui users. ;-)\n\nThe best we can do is let the user pick their TCL_PATH and\nTCLTK_PATH up in git's own Makefile, and have it pass down into\ngit-gui's Makefile when git-gui is being built from within git.\nThat is the arrangement we currently have.\n\n-- \nShawn.\n"},{"id":"45089","messageId":"20070614190739.GA3779@void.codelabs.ru","threadId":"8580","inReplyTo":"20070614150929.GA18491@spearce.org","subject":"Re: [CORRECTED PATCH] Introduce file with the common default build-time items.","fromName":"Eygene Ryabinkin","fromEmail":"rea-git@codelabs.ru","sentAt":"2007-06-14T19:07:39Z","receivedAt":"2007-06-14T19:07:39Z","isPatch":true,"sender":{"key":"rea-git@codelabs.ru","avatar":null},"body":"Shawn,\n\nThu, Jun 14, 2007 at 11:09:29AM -0400, Shawn O. Pearce wrote:\n> Eygene Ryabinkin wrote:\n> No, because Junio has already stated a desire to remove git-gui.git\n> from git.git and convert it to a proper subproject by the time of\n> Git 1.6. That means the git-gui/ subdirectory will become optional,\n> though I imagine most git-gui users will still have it. But not\n> all Git users are git-gui users. ;-)\n\nOK, it means that git-gui will be totally separated from the\ngit.git? And one will download it as the separate tarball?\n\n> The best we can do is let the user pick their TCL_PATH and\n> TCLTK_PATH up in git's own Makefile, and have it pass down into\n> git-gui's Makefile when git-gui is being built from within git.\n> That is the arrangement we currently have.\n\nOK, fine, thanks for the explanations. The corrected patch follows.\n\n-----\n\nWords 'wish' and 'tclsh' are scattered across at least three files,\nbut they are tied to the same entities. To ease the maintenance\nand remove errors, these configuration items were gathered into the\nseparate file named 'common-make-vars.def'.\n\nSigned-off-by: Eygene Ryabinkin \n---\n Makefile | 17 +++++++++++------\n common-make-vars.def | 11 +++++++++++\n configure.ac | 4 +++-\n 3 files changed, 25 insertions(+), 7 deletions(-)\n create mode 100644 common-make-vars.def\n\ndiff --git a/Makefile b/Makefile\nindex 6cd9ea2..e98f16b 100644\n--- a/Makefile\n+++ b/Makefile\n@@ -116,16 +116,21 @@ all::\n #\n # The TCL_PATH variable governs the location of the Tcl interpreter\n # used to optimize git-gui for your system. Only used if NO_TCLTK\n-# is not set. Defaults to the bare 'tclsh'.\n+# is not set. Defaults to the value of the __GIT_DEFAULT_TCLSH_NAME\n+# from common-make-vars.def.\n #\n-# The TCLTK_PATH variable governs the location of the Tcl/Tk interpreter.\n-# If not set it defaults to the bare 'wish'. If it is set to the empty\n-# string then NO_TCLTK will be forced (this is used by configure script).\n+# The TCLTK_PATH variable governs the location of the Tcl/Tk\n+# interpreter. If not set it defaults to the value of the\n+# __GIT_DEFAULT_TCLTK_NAME from common-make-vars.def. If it is set\n+# to the empty string then NO_TCLTK will be forced (this is used\n+# by configure script).\n #\n \n GIT-VERSION-FILE: .FORCE-GIT-VERSION-FILE\n \t@$(SHELL_PATH) ./GIT-VERSION-GEN\n -include GIT-VERSION-FILE\n+# Default values\n+-include common-make-vars.def\n \n uname_S := $(shell sh -c 'uname -s 2>/dev/null || echo not')\n uname_M := $(shell sh -c 'uname -m 2>/dev/null || echo not')\n@@ -177,8 +182,8 @@ AR ?= ar\n TAR ?= tar\n INSTALL ?= install\n RPMBUILD ?= rpmbuild\n-TCL_PATH ?= tclsh\n-TCLTK_PATH ?= wish\n+TCL_PATH ?= $(__GIT_DEFAULT_TCLSH_NAME)\n+TCLTK_PATH ?= $(__GIT_DEFAULT_TCLTK_NAME)\n \n export TCL_PATH TCLTK_PATH\n \ndiff --git a/common-make-vars.def b/common-make-vars.def\nnew file mode 100644\nindex 0000000..43a3a8b\n--- /dev/null\n+++ b/common-make-vars.def\n@@ -0,0 +1,11 @@\n+# This file is meant to be sourced from the autoconf script\n+# and included from the Makefile. It carries the default values\n+# to eliminate their redundancy across the files. The syntax\n+# is 'name=value' without extra spaces across the '=' sign to\n+# make shell happy. Symbols '#' are starting comments ;))\n+\n+# Default Tcl/Tk interpreter name\n+__GIT_DEFAULT_TCLTK_NAME=wish\n+\n+# Default Tcl interpreter name\n+__GIT_DEFAULT_TCLSH_NAME=tclsh\ndiff --git a/configure.ac b/configure.ac\nindex 50d2b85..fd1d241 100644\n--- a/configure.ac\n+++ b/configure.ac\n@@ -12,6 +12,8 @@ config_in=config.mak.in\n \n echo \"# ${config_append}. Generated by configure.\" > \"${config_append}\"\n \n+## Defaults\n+source common-make-vars.def\n \n ## Definitions of macros\n # GIT_CONF_APPEND_LINE(LINE)\n@@ -97,7 +99,7 @@ AC_CHECK_PROGS(TAR, [gtar tar])\n if test -z \"$NO_TCLTK\"; then\n if test \"$with_tcltk\" = \"\"; then\n # No Tcl/Tk switches given. Do not check for Tcl/Tk, use bare 'wish'.\n- TCLTK_PATH=wish\n+ TCLTK_PATH=${__GIT_DEFAULT_TCLTK_NAME}\n AC_SUBST(TCLTK_PATH)\n elif test \"$with_tcltk\" = \"yes\"; then\n # Tcl/Tk check requested.\n-- \n1.5.2.1\n"},{"id":"45106","messageId":"20070615032204.GC18491@spearce.org","threadId":"8580","inReplyTo":"20070614190739.GA3779@void.codelabs.ru","subject":"Re: [CORRECTED PATCH] Introduce file with the common default build-time items.","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-06-15T03:22:04Z","receivedAt":"2007-06-15T03:22:04Z","isPatch":true,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Eygene Ryabinkin wrote:\n> Thu, Jun 14, 2007 at 11:09:29AM -0400, Shawn O. Pearce wrote:\n> > Eygene Ryabinkin wrote:\n> > No, because Junio has already stated a desire to remove git-gui.git\n> > from git.git and convert it to a proper subproject by the time of\n> > Git 1.6. That means the git-gui/ subdirectory will become optional,\n> > though I imagine most git-gui users will still have it. But not\n> > all Git users are git-gui users. ;-)\n> \n> OK, it means that git-gui will be totally separated from the\n> git.git? And one will download it as the separate tarball?\n\nThat's one option. But Junio and I are also considering keeping\nit inside the git tarball as well, as many users have gotten used\nto it being in the core Git distribution. I think it all depends\non if myself (or someone else) adds subproject recursion support\ninto git-archive. ;-)\n\nNo subproject recusion in git-archive will probably mean git-gui\nwould get dropped from the core git tarball. Given we're talking\nabout 1.6 timeframe I think we might be able to get that feature\nworking by then.\n\n> > The best we can do is let the user pick their TCL_PATH and\n> > TCLTK_PATH up in git's own Makefile, and have it pass down into\n> > git-gui's Makefile when git-gui is being built from within git.\n> > That is the arrangement we currently have.\n> \n> OK, fine, thanks for the explanations. The corrected patch follows.\n \n...\n> Makefile | 17 +++++++++++------\n> common-make-vars.def | 11 +++++++++++\n> configure.ac | 4 +++-\n> 3 files changed, 25 insertions(+), 7 deletions(-)\n> create mode 100644 common-make-vars.def\n...\n\nI dunno. 25 insertions and 7 deletions to reduce two uses of 'wish'\ninto one use of 'wish'? That hardly seems worth the additional\n18 lines of code. Feels like code churn to me. And I rarely feel\ncode churn. I'm usually a lot more caviler about changing things\nthan Junio, Dscho, Nico, Linus, ...\n\n-- \nShawn.\n"},{"id":"45114","messageId":"20070615054002.GD3779@void.codelabs.ru","threadId":"8580","inReplyTo":"20070615032204.GC18491@spearce.org","subject":"Re: [CORRECTED PATCH] Introduce file with the common default build-time items.","fromName":"Eygene Ryabinkin","fromEmail":"rea-git@codelabs.ru","sentAt":"2007-06-15T05:40:02Z","receivedAt":"2007-06-15T05:40:02Z","isPatch":true,"sender":{"key":"rea-git@codelabs.ru","avatar":null},"body":"Shawn, good da.y\n\nThu, Jun 14, 2007 at 11:22:04PM -0400, Shawn O. Pearce wrote:\n> > OK, it means that git-gui will be totally separated from the\n> > git.git? And one will download it as the separate tarball?\n> \n> That's one option. But Junio and I are also considering keeping\n> it inside the git tarball as well, as many users have gotten used\n> to it being in the core Git distribution. I think it all depends\n> on if myself (or someone else) adds subproject recursion support\n> into git-archive. ;-)\n\nOK, I just wondered what to expect from the 1.6, since I am\ntrying to keep FreeBSD port in sync with the latest Git release.\n> ...\n> > Makefile | 17 +++++++++++------\n> > common-make-vars.def | 11 +++++++++++\n> > configure.ac | 4 +++-\n> > 3 files changed, 25 insertions(+), 7 deletions(-)\n> > create mode 100644 common-make-vars.def\n> ...\n> \n> I dunno. 25 insertions and 7 deletions to reduce two uses of 'wish'\n> into one use of 'wish'? That hardly seems worth the additional\n> 18 lines of code.\n\n11 of new lines are common-make-vars.def: it is heavily commented.\n\n> Feels like code churn to me. And I rarely feel\n> code churn. I'm usually a lot more caviler about changing things\n> than Junio, Dscho, Nico, Linus, ...\n\nOK, let us wait for the other's reaction. May be you're right and\nit doesn't worth it. But I always felt that if I can change something\nby changing it only in one place, then it worth it. Otherwise I\nshould remember all places where it is used and this leads to errors.\nBut maybe the 'wish' and 'tclsh' are not worth it.\n\nThank you!\n-- \nEygene\n"},{"id":"45116","messageId":"20070615055813.GG18491@spearce.org","threadId":"8580","inReplyTo":"20070615054002.GD3779@void.codelabs.ru","subject":"Re: [CORRECTED PATCH] Introduce file with the common default build-time items.","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-06-15T05:58:13Z","receivedAt":"2007-06-15T05:58:13Z","isPatch":true,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Eygene Ryabinkin wrote:\n> Thu, Jun 14, 2007 at 11:22:04PM -0400, Shawn O. Pearce wrote:\n> > > OK, it means that git-gui will be totally separated from the\n> > > git.git? And one will download it as the separate tarball?\n> > \n> > That's one option. But Junio and I are also considering keeping\n> > it inside the git tarball as well, as many users have gotten used\n> > to it being in the core Git distribution. I think it all depends\n> > on if myself (or someone else) adds subproject recursion support\n> > into git-archive. ;-)\n> \n> OK, I just wondered what to expect from the 1.6, since I am\n> trying to keep FreeBSD port in sync with the latest Git release.\n\nHeh. Got a crystal ball?\n\nI'm not sure anyone knows what the 1.6 release will look like yet.\nRight now I know we're trying to get the submodule user interface\nbuilt and stable, before we start eating that dogfood as part of\nthe core Git code itself. But we do want to be using our own tools\nto build our tools. ;-)\n\n1.6 is just a number thrown on the wall as its likely that by the\ntime we get around to having a release worthy of the name 1.6 enough\nusers will be running a 1.5.2 or newer that has at least some of\nthe basic plumbing and porcelain for subprojects that it wouldn't\nbe a problem if we started using it ourselves in the git.git project.\n\n-- \nShawn.\n"},{"id":"45118","messageId":"20070615060747.GE3779@void.codelabs.ru","threadId":"8580","inReplyTo":"20070615055813.GG18491@spearce.org","subject":"Re: [CORRECTED PATCH] Introduce file with the common default build-time items.","fromName":"Eygene Ryabinkin","fromEmail":"rea-git@codelabs.ru","sentAt":"2007-06-15T06:07:47Z","receivedAt":"2007-06-15T06:07:47Z","isPatch":true,"sender":{"key":"rea-git@codelabs.ru","avatar":null},"body":"Fri, Jun 15, 2007 at 01:58:13AM -0400, Shawn O. Pearce wrote:\n> > OK, I just wondered what to expect from the 1.6, since I am\n> > trying to keep FreeBSD port in sync with the latest Git release.\n> \n> Heh. Got a crystal ball?\n\nSort of: when time will come and new release will be out, various\nrumors I heard might help me to get the release to be ported quickly.\nAt least I hope so ;)\n-- \nEygene\n"},{"id":"45122","messageId":"46723C9F.4EE044F9@eudaptics.com","threadId":"8580","inReplyTo":"20070615054002.GD3779@void.codelabs.ru","subject":"Re: [CORRECTED PATCH] Introduce file with the common default build-time items.","fromName":"Johannes Sixt","fromEmail":"j.sixt@eudaptics.com","sentAt":"2007-06-15T07:15:43Z","receivedAt":"2007-06-15T07:15:43Z","isPatch":true,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Eygene Ryabinkin wrote:\n> OK, let us wait for the other's reaction. May be you're right and\n> it doesn't worth it. But I always felt that if I can change something\n> by changing it only in one place, then it worth it. Otherwise I\n> should remember all places where it is used and this leads to errors.\n> But maybe the 'wish' and 'tclsh' are not worth it.\n\nHuh? This \"one place\" already exists. Its name is 'config.mak'. I have\nthis in it:\n\nTCL_PATH=tclsh84\nTCLTK_PATH=wish84\n\n-- Hannes\n"},{"id":"45129","messageId":"20070615102847.GF3779@void.codelabs.ru","threadId":"8580","inReplyTo":"46723C9F.4EE044F9@eudaptics.com","subject":"Re: [CORRECTED PATCH] Introduce file with the common default build-time items.","fromName":"Eygene Ryabinkin","fromEmail":"rea-git@codelabs.ru","sentAt":"2007-06-15T10:28:48Z","receivedAt":"2007-06-15T10:28:48Z","isPatch":true,"sender":{"key":"rea-git@codelabs.ru","avatar":null},"body":"Johannes, good day.\n\nFri, Jun 15, 2007 at 09:15:43AM +0200, Johannes Sixt wrote:\n> Eygene Ryabinkin wrote:\n> > OK, let us wait for the other's reaction. May be you're right and\n> > it doesn't worth it. But I always felt that if I can change something\n> > by changing it only in one place, then it worth it. Otherwise I\n> > should remember all places where it is used and this leads to errors.\n> > But maybe the 'wish' and 'tclsh' are not worth it.\n> \n> Huh? This \"one place\" already exists. Its name is 'config.mak'. I have\n> this in it:\n> \n> TCL_PATH=tclsh84\n> TCLTK_PATH=wish84\n\nconfig.mak is a bit different: it is not used by the configure when\nit sets the default TCL_PATH. But ok, I feel that my change is not\nvery good, since two of you already disliked it. Please, don't\nwaste your time on it anymore.\n-- \nEygene\n"}]}