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

Add dev support instructions for Arch Linux! #1614

Merged
merged 1 commit into from Jan 4, 2017

Conversation

Projects
None yet
6 participants
@fnichol
Member

fnichol commented Jan 4, 2017

A few members of the core team have been working on Arch Linux VMs to
get better IO performance on recompiles. This addition to the
BUILDING.md document helps other developers to reproduce our work.

gif-keyboard-2461390727278928669

Add dev support instructions for Arch Linux!
A few members of the core team have been working on Arch Linux VMs to
get better IO performance on recompiles. This addition to the
`BUILDING.md` document helps other developers to reproduce our work.

Signed-off-by: Fletcher Nichol <fnichol@nichol.ca>

@fnichol fnichol added the Chore label Jan 4, 2017

@thesentinels

This comment has been minimized.

Show comment
Hide comment
@thesentinels

thesentinels Jan 4, 2017

Contributor

Thanks for the pull request! Here is what will happen next:

  1. Your PR will be reviewed by the maintainers
  2. If everything looks good, one of them will approve it, and your PR will be merged.

Thank you for contributing!

Contributor

thesentinels commented Jan 4, 2017

Thanks for the pull request! Here is what will happen next:

  1. Your PR will be reviewed by the maintainers
  2. If everything looks good, one of them will approve it, and your PR will be merged.

Thank you for contributing!

@fnichol

This comment has been minimized.

Show comment
Hide comment
@fnichol

fnichol Jan 4, 2017

Member

@adamhjk Does this look pretty close to you? I'm getting builds and tests running very nicely.

Member

fnichol commented Jan 4, 2017

@adamhjk Does this look pretty close to you? I'm getting builds and tests running very nicely.

@adamhjk

This comment has been minimized.

Show comment
Hide comment
@adamhjk

adamhjk Jan 4, 2017

Contributor

Yeah, this looks perfect.

gif-keyboard-1314491673220304369

Contributor

adamhjk commented Jan 4, 2017

Yeah, this looks perfect.

gif-keyboard-1314491673220304369

@fnichol

This comment has been minimized.

Show comment
Hide comment
@fnichol
Member

fnichol commented Jan 4, 2017

@thesentinels approve

@thesentinels

This comment has been minimized.

Show comment
Hide comment
@thesentinels

thesentinels Jan 4, 2017

Contributor

🤘 I am testing your branch against master before merging it. We do this to ensure that the master branch is never failing tests.

Contributor

thesentinels commented Jan 4, 2017

🤘 I am testing your branch against master before merging it. We do this to ensure that the master branch is never failing tests.

@thesentinels

This comment has been minimized.

Show comment
Hide comment
@thesentinels

thesentinels Jan 4, 2017

Contributor

:neckbeard: Travis CI has started testing this PR.

Contributor

thesentinels commented Jan 4, 2017

:neckbeard: Travis CI has started testing this PR.

@thesentinels

This comment has been minimized.

Show comment
Hide comment
@thesentinels

thesentinels Jan 4, 2017

Contributor

💖 Travis CI reports this PR passed.

It always makes me feel nice when humans approve of one anothers work. I'm merging this PR now.

I just want you and the contributor to answer me one question:

gif-keyboard-3280869874741411265

Contributor

thesentinels commented Jan 4, 2017

💖 Travis CI reports this PR passed.

It always makes me feel nice when humans approve of one anothers work. I'm merging this PR now.

I just want you and the contributor to answer me one question:

gif-keyboard-3280869874741411265

@thesentinels thesentinels merged commit 8ea51ef into master Jan 4, 2017

3 checks passed

DCO This commit has a DCO Signed-off-by line
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details

@thesentinels thesentinels deleted the fnichol/dev-on-arch branch Jan 4, 2017

@adamhjk

This comment has been minimized.

Show comment
Hide comment
@adamhjk

adamhjk Jan 5, 2017

Contributor

@thesentinels approve

Contributor

adamhjk commented Jan 5, 2017

@thesentinels approve

@thesentinels

This comment has been minimized.

Show comment
Hide comment
@thesentinels

thesentinels Jan 5, 2017

Contributor

🤘 I am testing your branch against master before merging it. We do this to ensure that the master branch is never failing tests.

Contributor

thesentinels commented Jan 5, 2017

🤘 I am testing your branch against master before merging it. We do this to ensure that the master branch is never failing tests.

@thesentinels

This comment has been minimized.

Show comment
Hide comment
@thesentinels

thesentinels Jan 5, 2017

Contributor

Sorry; I had a problem testing this pull request. The error was:

Expected process to exit with [0], but received '128'
---- Begin output of git fetch origin pull/1614/merge ----
STDOUT: 
STDERR: Warning: Permanently added 'github.com,192.30.253.112' (RSA) to the list of known hosts.
fatal: Couldn't find remote ref pull/1614/merge
---- End output of git fetch origin pull/1614/merge ----
Ran git fetch origin pull/1614/merge returned 128

Oops

Contributor

thesentinels commented Jan 5, 2017

Sorry; I had a problem testing this pull request. The error was:

Expected process to exit with [0], but received '128'
---- Begin output of git fetch origin pull/1614/merge ----
STDOUT: 
STDERR: Warning: Permanently added 'github.com,192.30.253.112' (RSA) to the list of known hosts.
fatal: Couldn't find remote ref pull/1614/merge
---- End output of git fetch origin pull/1614/merge ----
Ran git fetch origin pull/1614/merge returned 128

Oops

@ShalokShalom

This comment has been minimized.

Show comment
Hide comment
@ShalokShalom

ShalokShalom Feb 3, 2017

@thesentinels Did you solve this?

ShalokShalom commented Feb 3, 2017

@thesentinels Did you solve this?

@smurawski

This comment has been minimized.

Show comment
Hide comment
@smurawski

smurawski Feb 3, 2017

Contributor

@ShalokShalom there were dueling approves, so the second check was trying to use a branch that had been deleted because it was already merged.

Contributor

smurawski commented Feb 3, 2017

@ShalokShalom there were dueling approves, so the second check was trying to use a branch that had been deleted because it was already merged.

@ShalokShalom

This comment has been minimized.

Show comment
Hide comment
@ShalokShalom

ShalokShalom Feb 3, 2017

Thanks a lot.

I am a newbie and like to understand, if that is a benefit for Habitat binarys, which run on Arch and/or for developers who create Habitat packages on Arch?

And in both cases: Why effect this one single distribution?

More precisely: What is an Arch VM?

Thanks a lot in advance

ShalokShalom commented Feb 3, 2017

Thanks a lot.

I am a newbie and like to understand, if that is a benefit for Habitat binarys, which run on Arch and/or for developers who create Habitat packages on Arch?

And in both cases: Why effect this one single distribution?

More precisely: What is an Arch VM?

Thanks a lot in advance

@smurawski

This comment has been minimized.

Show comment
Hide comment
@smurawski

smurawski Feb 3, 2017

Contributor

@ShalokShalom This is about instructions for developing for this project on Arch linux (as several of the project developers are using that distribution). Habitat packages in general are distribution agnostic.

If you'd like to chat more about specifics, we've got Discourse-based forums and a Slack channel which you can connect to via https://www.habitat.sh/community/

There are also docs at https://www.habitat.sh/docs/overview/ which walk throught the habitat concepts and include some walkthroughs.

Contributor

smurawski commented Feb 3, 2017

@ShalokShalom This is about instructions for developing for this project on Arch linux (as several of the project developers are using that distribution). Habitat packages in general are distribution agnostic.

If you'd like to chat more about specifics, we've got Discourse-based forums and a Slack channel which you can connect to via https://www.habitat.sh/community/

There are also docs at https://www.habitat.sh/docs/overview/ which walk throught the habitat concepts and include some walkthroughs.

@ShalokShalom

This comment has been minimized.

Show comment
Hide comment
@ShalokShalom

ShalokShalom Feb 3, 2017

Thanks a lot, that makes it clear to me. 👍

I was a bit confused, since Habitat is distro agnostic on the users side.

ShalokShalom commented Feb 3, 2017

Thanks a lot, that makes it clear to me. 👍

I was a bit confused, since Habitat is distro agnostic on the users side.

@eeyun eeyun added C-chore and removed Chore labels Jun 6, 2017

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