From: Todd Zullinger <tmz@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>, git <git@vger.kernel.org>,
Dominik Mahrer <teddy@teddy.ch>,
git-packagers@googlegroups.com,
Christian Couder <chriscool@tuxfamily.org>,
Jeff King <peff@peff.net>,
Lars Schneider <larsxschneider@gmail.com>
Subject: Re: [PATCH] travis-ci: avoid new tcl/tk build requirement
Date: Tue, 28 Nov 2017 11:02:22 -0500 [thread overview]
Message-ID: <20171128160222.GO3693@zaya.teonanacatl.net> (raw)
In-Reply-To: <CAP8UFD1Y_7FcARFoqNKTpDLRxKW1+jCBGAy5+TxL33ui0Hyb8w@mail.gmail.com>
Christian Couder wrote:
>> Junio C Hamano wrote:
>>> It seems that TravisCI objects ;-)
>>>
>>> https://travis-ci.org/git/git/jobs/307745929
>>
>> Interesting that the main builds passed. I don't know what the default
>> 64-bit linuxinstall looks like in travis, so I presume it includes
>> tcl/tk or something.
>
> Yeah, interesting. I am cc'ing Lars who perhaps knows.
I pulled the travis docker image used in clang/gcc builds[1] and can
see it has both tcl and tk packages installed. The linux32 builds use
a docker image[2] which does not contain tcl or tk.
[1] travisci/ci-garnet:packer-1503972846
[2] daald/ubuntu32:xenial
If we wanted, we could set BYPASS_TCLTK_CHECK only for the linux32
builds. I think it's probably better to do it globally rather than
rely on the travis containers implicitly having tcl/tk installed.
> The patch looks good to me. Thanks!
>
> I wonder if it would be better to squash it into my patch or to keep
> it separate. I am ok with both ways.
I fine either way too. This is still just on pu, so squashing it in
seems like the way to go. I only made it separate to cause travis to
run the tests. :)
--
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In the beginning the Universe was created. This has made a lot of
people very angry and has been widely regarded as a bad move.
-- Douglas Adams
next prev parent reply other threads:[~2017-11-28 16:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 17:15 [PATCH] Makefile: check that tcl/tk is installed Christian Couder
2017-11-20 17:17 ` Christian Couder
2017-11-20 19:19 ` Jonathan Nieder
2017-11-20 23:58 ` Christian Couder
2017-11-26 19:15 ` Jeff King
2017-11-26 20:57 ` Christian Couder
2017-11-27 15:31 ` Jeff King
2017-11-27 1:13 ` Junio C Hamano
2017-11-27 4:31 ` Junio C Hamano
2017-11-27 4:35 ` Jeff King
2017-11-27 5:22 ` Todd Zullinger
2017-11-27 8:24 ` Christian Couder
2017-11-27 15:27 ` Jeff King
2017-11-27 23:42 ` Junio C Hamano
2017-11-28 4:35 ` Junio C Hamano
2017-11-28 14:37 ` [PATCH] travis-ci: avoid new tcl/tk build requirement Todd Zullinger
2017-11-28 15:03 ` Christian Couder
2017-11-28 16:02 ` Todd Zullinger [this message]
2017-11-28 23:47 ` Junio C Hamano
2017-11-27 9:08 ` [PATCH] Makefile: check that tcl/tk is installed Junio C Hamano
2017-11-25 20:46 ` Christian Couder
2017-11-26 3:53 ` Junio C Hamano
2017-11-26 14:00 ` Christian Couder
2017-11-26 17:43 ` Ramsay Jones
2017-11-26 18:34 ` Christian Couder
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171128160222.GO3693@zaya.teonanacatl.net \
--to=tmz@pobox.com \
--cc=chriscool@tuxfamily.org \
--cc=christian.couder@gmail.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=larsxschneider@gmail.com \
--cc=peff@peff.net \
--cc=teddy@teddy.ch \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).