New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Instructions on how to install github-gem on Windows #4975

Merged
merged 2 commits into from Jun 2, 2016

Conversation

Projects
None yet
4 participants
@jwillmer
Contributor

jwillmer commented Jun 2, 2016

I added a line to a blog post I wrote because it took me 3 days to figure it out.

@envygeeks

This comment has been minimized.

Show comment
Hide comment
@envygeeks

envygeeks Jun 2, 2016

Contributor

I don't know what the @jekyll/ecosystem and @jekyll/core wish for this kind of thing but I would much rather prefer the directions be embedded directly in the page with a link back to your site as the credit, this reduces the friction to solving a problem IMO.

Contributor

envygeeks commented Jun 2, 2016

I don't know what the @jekyll/ecosystem and @jekyll/core wish for this kind of thing but I would much rather prefer the directions be embedded directly in the page with a link back to your site as the credit, this reduces the friction to solving a problem IMO.

@jwillmer

This comment has been minimized.

Show comment
Hide comment
@jwillmer

jwillmer Jun 2, 2016

Contributor

Sure, I can add it direct to the docs I only did it this way because I saw that in the windows installation instructions the instructions are also only linked.

Contributor

jwillmer commented Jun 2, 2016

Sure, I can add it direct to the docs I only did it this way because I saw that in the windows installation instructions the instructions are also only linked.

@parkr

This comment has been minimized.

Show comment
Hide comment
@parkr

parkr Jun 2, 2016

Member

Let's wait on that – the instructions there have a hard dependency on Chocolatey which I haven't heard of. Linking out is fine for now. 😄

@jekyllbot: merge +site

Member

parkr commented Jun 2, 2016

Let's wait on that – the instructions there have a hard dependency on Chocolatey which I haven't heard of. Linking out is fine for now. 😄

@jekyllbot: merge +site

@jekyllbot jekyllbot merged commit 1e22c36 into jekyll:master Jun 2, 2016

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

jekyllbot added a commit that referenced this pull request Jun 2, 2016

@parkr parkr removed the pending-feedback label Jun 2, 2016

@jwillmer jwillmer deleted the jwillmer:patch-1 branch Jun 2, 2016

@envygeeks

This comment has been minimized.

Show comment
Hide comment
@envygeeks

envygeeks Jun 2, 2016

Contributor

@spudowiar by that logic then we should throw out all directions mentioning boxen, and the other mac packages since they are non-essential.

@parkr @spudowiar as I'm sure @jwillmer already knows, Microsoft has pretty much endorsed Chocolately and even has mentioned it in their own docs, also, as far as I'm aware Microsofts own CLI package manager even has compatibility with it.

Not saying we shouldn't include it, just saying that Chocolatey is to Windows what Boxen/Homebrew is to OS X except in this case it's actually somewhat integrated into the system from the operating itself. As an example, this can be done on an out-of-box Windows install:

get-packageprovider -name chocolatey
install-package vlc

Maybe the post should be updated to switch to native Windows cmdlets on Windows 10 (with directions on how to install OneGet on Windows 7/8 -- it's open source and available from Microsoft for both?)

Contributor

envygeeks commented Jun 2, 2016

@spudowiar by that logic then we should throw out all directions mentioning boxen, and the other mac packages since they are non-essential.

@parkr @spudowiar as I'm sure @jwillmer already knows, Microsoft has pretty much endorsed Chocolately and even has mentioned it in their own docs, also, as far as I'm aware Microsofts own CLI package manager even has compatibility with it.

Not saying we shouldn't include it, just saying that Chocolatey is to Windows what Boxen/Homebrew is to OS X except in this case it's actually somewhat integrated into the system from the operating itself. As an example, this can be done on an out-of-box Windows install:

get-packageprovider -name chocolatey
install-package vlc

Maybe the post should be updated to switch to native Windows cmdlets on Windows 10 (with directions on how to install OneGet on Windows 7/8 -- it's open source and available from Microsoft for both?)

@envygeeks

This comment has been minimized.

Show comment
Hide comment
Contributor

envygeeks commented Jun 2, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment