Added instructions to _includes/setup.html on how to install Make. #533

mikej888 · 2014-06-09T14:46:46Z

No description provided.

wking · 2014-06-09T21:24:39Z

On Mon, Jun 09, 2014 at 07:46:47AM -0700, mikej888 wrote:

Added Make instructions to _includes/setup.html

Can't we just have folks install msysGit from the start, instead of
installing the more limited Git for Windows? I looked at
https://github.com/msysgit/msysgit/releases/tag/Git-1.9.2-preview20140411
anyway, and msysgit-Git-1.9.2-preview20140411.tar.gz certainly has
make.exe.

mikej888 · 2014-06-10T14:05:22Z

I can't see make.exe anywhere within Git-1.9.2-preview20140411.exe once unpacked and installed.

I'd be concerned about having attendees install the full mysysGit as it's a hefty 2GB versus 250MB, is missing wget, and is billed as "for developers who want to contribute by writing code for Git for Windows" rather than Windows users who want to use Git.

wking · 2014-06-10T16:34:50Z

On Tue, Jun 10, 2014 at 07:05:22AM -0700, mikej888 wrote:

I can't see make.exe anywhere within Git-1.9.2-preview20140411.exe
once unpacked and installed.

Ah, maybe the “Git for Windows” installers are trimmed back down, and
not just an alternatively packagaged version of the source tarball?

I'd be concerned about having attendees install the full mysysGit as
it's a hefty 2GB versus 250MB,

Disk space is cheap, and all that extra stuff is build dependencies.
The stuff that Git needs to build is usually good stuff ;).

is missing wget,

It has curl, so missing wget is not critical.

and is billed as "for developers who want to contribute by writing
code for Git for Windows" rather than Windows users who want to use
Git.

I'd read that as “for developers who want to compile stuff using Make,
Perl, C, and other *nix-y stuff”, which sounds like a fair match for
our students. Of course, cherry-picking the stuff we actually need
for a given boot camp would be nice, but unless we want to package it
up for folks on a per-workshop level, I think it's easier to just have
them install the whole thing.

gvwilson · 2014-06-11T22:46:08Z

Happy to include these instructions, but:

Should we put a copy of make.exe in http://files.software-carpentry.org so that we have a more memorable (and more stable) URL?
Can we do that for Mac OS X as well? (Is it legal, and would its dependencies reliably resolve?) I'd like to avoid requiring people to download XCode if possible.

wking · 2014-06-11T23:58:43Z

On Wed, Jun 11, 2014 at 03:46:09PM -0700, Greg Wilson wrote:

Should we put a copy of make.exe in
http://files.software-carpentry.org so that we have a more
memorable (and more stable) URL?

Can we do that for Mac OS X as well? (Is it legal, and would its
dependencies reliably resolve?) I'd like to avoid requiring people
to download XCode if possible.

I don't think we can do either legally without also distributing the
source for GNU Make (which is under the GPLv3+ 1). I'm skeptical
that the approach taken by msysGit is legal. Distributing the source
wouldn't be hard, but we'd need to compile it ourselves (since msysGit
doesn't link to the source they used) or find someone else who is
distributing binaries along with their sources.

I think getting into the binary-packaging world ourselves isn't going
to be a high-impact approach though. If there isn't anybody else
already providing binaries that we can point folks to, we're probably
going about things the wrong way ;).

mikej888 · 2014-06-13T08:22:01Z

I aqree with avoiding getting into building binaries that are available elsewhere.

Disk space is cheap but 2GB is still a big ask - attendees laptops can be quite old and limited in terms of space. I'd be more open to mysysGit if it was explicitly promoted as a Linuxy software development environment (rather than an environment for Git developers that has some useful Linuxy tools included). Could we not give them the choice and explain the trade-off?

mikej888 · 2014-06-13T09:34:07Z

About Mac and XCode, it appears there is a Command Line Tools for XCode bundle which contains make and other useful tools, which is now distributed separately from XCode:

Or see notes in

http://www.computersnyou.com/2025/2013/06/install-command-line-tools-in-osx-10-9-mavericks-how-to/

wking · 2014-06-13T15:54:34Z

On Fri, Jun 13, 2014 at 01:22:01AM -0700, mikej888 wrote:

I'd be more open to mysysGit if it was explicitly promoted as a
Linuxy software development environment (rather than an environment
for Git developers that has some useful Linuxy tools included).

Perhaps we can try bumping our dependency up to MSYS itself 1?
That's a generic GNU-for-Windows packaging system 2, but it probably
won't play nicely with msysGit 3. There has been work on pulling
MSYS and a Git build back together 4, but I don't know how reliable
it is yet.

Could we not give them the choice and explain the trade-off?

You can ask, but my impression is that the both the MSYS and msysGit
developers are completly swamped 3, and won't be receptive to
requests for broader scoping.

In the end, swapping out the whole kernel (with it's UNIX-derived
APIs) for Windows' native APIs is a tough task, and folks who want to
use *nix software seem to prefer just using a *nix kernel ;).
Personally I think it would be more productive to focus on bootable
SWC media if we want students to have an environment they can take
home with them 5.

mikej888 · 2014-06-13T17:51:47Z

Could we not give them the choice and explain the trade-off?
You can ask, but my impression is that the both the MSYS and msysGit
developers are completly swamped [3], and won't be receptive to
requests for broader scoping.

Sorry, I meant give boot camp attendees the choice of the two downloads so they can choose whether to opt for two downloads (Git for Windows + Make) or the one much larger one.

Personally I think it would be more productive to focus on bootable
SWC media if we want students to have an environment they can take
home with them [5].

That sounds good.

wking · 2014-06-13T18:04:40Z

On Fri, Jun 13, 2014 at 10:51:48AM -0700, mikej888 wrote:

Sorry, I meant give boot camp attendees the choice of the two
downloads so they can choose whether to opt for two downloads (Git
for Windows + Make) or the one much larger one.

Ah. If we really want Make and can't require msysGit, it would be
easy to add to add a make.exe download to our
swc-windows-installer.py. I just don't want to grow that script when
we are able to offload maintenance onto someone outside of SWC ;).

Personally I think it would be more productive to focus on
bootable SWC media if we want students to have an environment they
can take home with them [5].

That sounds good.

If you'd actually use something like this, I'll build a more current
ISO for you. The last time I proposed this approach, the response was
“meh” ;). Although as our suggested software enviroment gets more
complicated (KDiff3? #527), maybe we're approaching the tipping point
where some folks are ready to drop support for native Windows
installs. In that case, I prefer my ISOs to virtual machines for
folks with older hardware.

The whole msysGit dev environment is large [1]: On Fri, Jun 13, 2014 at 01:22:01AM -0700, Mike Jackson wrote: > Disk space is cheap but 2GB is still a big ask - attendees laptops > can be quite old and limited in terms of space. And may be difficult to install than the Git for Windows packaging [2]: On Fri, Aug 15, 2014 at 12:46:21PM -0700, Ethan White wrote: > My concern with installing msysGit is that the installer process > was substantially more complicated (at least the last time I > looked 6-12 months ago). My concern is that folks will get hung up > on all of the options and at best feel confused/overwhelmed and at > worse not end up with a working install. Since that simple option (replace Git for Windows with the full msysGit) isn't available, with this commit we just grab the Make executable from the msysGit repository. To make grabbing additional binaries easier, I've implemented this with the generic install_msysgit_binary. I've also pinned the download to the most recent tag (Git-1.9.4-preview20140815), to keep the sha1 from changing under our feet. However, the make.exe binary was last touched on 2012-01-26 [3] and the last hash-changing commit was on 2007-08-06 [4], so it's not exactly a high-churn target ;). It would be nice if Windows came with a package manager (or even if msysGit was compatible with the upstream MSYS [5]) so we didn't have to jump through all these hoops. [1]: swcarpentry/DEPRECATED-bc#533 (comment) [2]: swcarpentry#6 (comment) [3]: msysgit/msysgit@cb9836b [4]: msysgit/msysgit@2914373 [5]: http://thread.gmane.org/gmane.comp.version-control.git/246514/focus=20055 Subject: Re: Re: [ANNOUNCE] WinGit - native x86/x64 Git for Windows From: Heiko Voigt <hvoigt@hvoigt.net> Date: 2014-04-19 18:42:10 GMT part of a thread started with [6]. [6]: http://thread.gmane.org/gmane.comp.version-control.git/245734 Subject: [ANNOUNCE] WinGit - native x86/x64 Git for Windows From: Marat Radchenko <marat@slonopotamus.org> Date: 2014-04-03 13:18:50 GMT

The whole msysGit dev environment is large [1]: On Fri, Jun 13, 2014 at 01:22:01AM -0700, Mike Jackson wrote: > Disk space is cheap but 2GB is still a big ask - attendees laptops > can be quite old and limited in terms of space. And may be more difficult to install than the Git for Windows packaging [2]: On Fri, Aug 15, 2014 at 12:46:21PM -0700, Ethan White wrote: > My concern with installing msysGit is that the installer process > was substantially more complicated (at least the last time I > looked 6-12 months ago). My concern is that folks will get hung up > on all of the options and at best feel confused/overwhelmed and at > worse not end up with a working install. Since that simple option (replace Git for Windows with the full msysGit) isn't available, with this commit we just grab the Make executable from the msysGit repository. To make grabbing additional binaries easier, I've implemented this with the generic install_msysgit_binary. I've also pinned the download to the most recent tag (Git-1.9.4-preview20140815), to keep the sha1 from changing under our feet. However, the make.exe binary was last touched on 2012-01-26 [3] and the last hash-changing commit was on 2007-08-06 [4], so it's not exactly a high-churn target ;). It would be nice if Windows came with a package manager (or even if msysGit was compatible with the upstream MSYS [5]) so we didn't have to jump through all these hoops. [1]: swcarpentry/DEPRECATED-bc#533 (comment) [2]: swcarpentry#6 (comment) [3]: msysgit/msysgit@cb9836b [4]: msysgit/msysgit@2914373 [5]: http://thread.gmane.org/gmane.comp.version-control.git/246514/focus=20055 Subject: Re: Re: [ANNOUNCE] WinGit - native x86/x64 Git for Windows From: Heiko Voigt <hvoigt@hvoigt.net> Date: 2014-04-19 18:42:10 GMT part of a thread started with [6]. [6]: http://thread.gmane.org/gmane.comp.version-control.git/245734 Subject: [ANNOUNCE] WinGit - native x86/x64 Git for Windows From: Marat Radchenko <marat@slonopotamus.org> Date: 2014-04-03 13:18:50 GMT

wking · 2014-09-29T17:39:17Z

On Mon, Sep 29, 2014 at 03:57:26AM -0700, Greg Wilson wrote:

Assigned #533 to @wking.

Since swcarpentry/windows-installer#21 the installed installs Make.
We just need to cut a new release of the installer.

gvwilson · 2014-09-29T17:49:40Z

Thanks - please go ahead and cut, then close this ticket.
Much appreciated,
G

wking · 2014-09-29T18:20:27Z

On Mon, Sep 29, 2014 at 10:49:41AM -0700, Greg Wilson wrote:

Thanks - please go ahead and cut, then close this ticket.

@ethanwhite has the Windows machine and Inno Setup installer needed to
build the new version. See swcarpentry/windows-installer#12. We need:

A pre-release mail to discuss@ for anyone interested in
beta-testing the Python script.
A merge from python → master
Tagging that merge as v0.2
Building the v0.2 installer with Inno Setup
Pushing the built installer to the windows-installer releases
Pushing the build installer to files.software-carpentry.org
A post-release mail to discuss@

The new Make install is the only significant change since v0.1.

ethanwhite · 2014-09-30T02:53:19Z

@wking If you'll take 1-3 and 7, I'll take 4-6.

wking · 2014-09-30T16:38:38Z

On Mon, Sep 29, 2014 at 11:20:24AM -0700, W. Trevor King wrote:

A pre-release mail to discuss@ for anyone interested in
beta-testing the Python script.

Done 1. I'll wait the week or two mentioned in that email before
moving on to step 2.

wking · 2014-10-18T17:51:27Z

On Mon, Sep 29, 2014 at 11:20:24AM -0700, W. Trevor King wrote:

A merge from python → master

Tagging that merge as v0.2

The mailing list message has cooked long enough (and turned up
swcarpentry/windows-installer#23). I've just completed these two
steps, so it's up to @ethanwhite to handle 4–6:

Building the v0.2 installer with Inno Setup

Pushing the built installer to the windows-installer releases

Pushing the build installer to files.software-carpentry.org

Let me know when that's done and I'll do 7:

A post-release mail to discuss@

wking · 2014-10-25T19:44:26Z

On Sat, Oct 18, 2014 at 10:41:42AM -0700, W. Trevor King wrote:

I've just completed these two steps, so it's up to @ethanwhite to
handle 4–6:

Mon, Sep 29, 2014 at 11:20:24AM -0700, W. Trevor King:

Building the v0.2 installer with Inno Setup

Pushing the built installer to the windows-installer releases

Pushing the build installer to files.software-carpentry.org

Let me know when that's done and I'll do 7:

A post-release mail to discuss@

@ethanwhite? This is a one-week bump, let me know if you prefer a
different frequency ;).

ethanwhite · 2014-11-01T19:05:00Z

Apologies for the delay (it's been quite the semester).

4 and 5 are now done and @gvwilson has been asked with 6.

On Sat, Oct 25, 2014 at 1:44 PM, W. Trevor King notifications@github.com
wrote:

On Sat, Oct 18, 2014 at 10:41:42AM -0700, W. Trevor King wrote:

I've just completed these two steps, so it's up to @ethanwhite to
handle 4–6:

Mon, Sep 29, 2014 at 11:20:24AM -0700, W. Trevor King:

Building the v0.2 installer with Inno Setup

Pushing the built installer to the windows-installer releases

Pushing the build installer to files.software-carpentry.org

Let me know when that's done and I'll do 7:

A post-release mail to discuss@

@ethanwhite? This is a one-week bump, let me know if you prefer a
different frequency ;).

—
Reply to this email directly or view it on GitHub
#533 (comment).

wking · 2014-11-01T19:10:06Z

On Sat, Nov 01, 2014 at 12:05:01PM -0700, Ethan White wrote:

Apologies for the delay (it's been quite the semester).

No worries ;). I'll try to remember to bump AppVersion before tagging
the master branch next time :p.

ethanwhite · 2014-11-02T20:13:06Z

has now been completed to well, so go ahead and make the announcement.

Ethan

On Sat, Nov 1, 2014 at 1:10 PM, W. Trevor King notifications@github.com
wrote:

On Sat, Nov 01, 2014 at 12:05:01PM -0700, Ethan White wrote:

Apologies for the delay (it's been quite the semester).

No worries ;). I'll try to remember to bump AppVersion before tagging
the master branch next time :p.

—
Reply to this email directly or view it on GitHub
#533 (comment).

wking · 2014-11-03T16:14:35Z

On Sun, Nov 02, 2014 at 12:13:06PM -0800, Ethan White wrote:

has now been completed to well, so go ahead and make the
announcement.

Done 1.

gvwilson · 2016-02-03T16:15:01Z

Relocate to the new Make lesson?

Added Make instructions to _includes/setup.html

f9974d6

Merge branch 'master' of https://github.com/swcarpentry/bc

b055b28

gvwilson added tools labels Jun 20, 2014

mikej888 mentioned this pull request Jul 3, 2014

Create lesson on Make. #556

Closed

4 tasks

wking mentioned this pull request Jul 4, 2014

Please add make to installed utilities swcarpentry/windows-installer#6

Closed

wking mentioned this pull request Sep 19, 2014

swc-windows-installer.py: Add install_msysgit_binary and install Make swcarpentry/windows-installer#21

Merged

gvwilson assigned wking Sep 29, 2014

mikej888 mentioned this pull request Jul 2, 2015

Make installation instructions carpentries/workshop-template#228

Closed

gvwilson unassigned wking Feb 3, 2016

gvwilson closed this Feb 3, 2016

gvwilson unassigned wking Feb 3, 2016

mikej888 mentioned this pull request Feb 10, 2016

Added section for Make setup carpentries/workshop-template#297

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Added instructions to _includes/setup.html on how to install Make. #533

Added instructions to _includes/setup.html on how to install Make. #533

mikej888 commented Jun 9, 2014

wking commented Jun 9, 2014

mikej888 commented Jun 10, 2014

wking commented Jun 10, 2014

gvwilson commented Jun 11, 2014

wking commented Jun 11, 2014

mikej888 commented Jun 13, 2014

mikej888 commented Jun 13, 2014

wking commented Jun 13, 2014

mikej888 commented Jun 13, 2014

wking commented Jun 13, 2014

wking commented Sep 29, 2014

gvwilson commented Sep 29, 2014

wking commented Sep 29, 2014

ethanwhite commented Sep 30, 2014

wking commented Sep 30, 2014

wking commented Oct 18, 2014

wking commented Oct 25, 2014

ethanwhite commented Nov 1, 2014

wking commented Nov 1, 2014

ethanwhite commented Nov 2, 2014

wking commented Nov 3, 2014

gvwilson commented Feb 3, 2016

Added instructions to _includes/setup.html on how to install Make. #533

Added instructions to _includes/setup.html on how to install Make. #533

Conversation

mikej888 commented Jun 9, 2014

wking commented Jun 9, 2014

mikej888 commented Jun 10, 2014

wking commented Jun 10, 2014

gvwilson commented Jun 11, 2014

wking commented Jun 11, 2014

mikej888 commented Jun 13, 2014

mikej888 commented Jun 13, 2014

wking commented Jun 13, 2014

mikej888 commented Jun 13, 2014

wking commented Jun 13, 2014

wking commented Sep 29, 2014

gvwilson commented Sep 29, 2014

wking commented Sep 29, 2014

ethanwhite commented Sep 30, 2014

wking commented Sep 30, 2014

wking commented Oct 18, 2014

wking commented Oct 25, 2014

ethanwhite commented Nov 1, 2014

wking commented Nov 1, 2014

ethanwhite commented Nov 2, 2014

wking commented Nov 3, 2014

gvwilson commented Feb 3, 2016