Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Provide a start script for a setup based on nixpkgs #784

Closed
Profpatsch opened this issue Mar 27, 2019 · 2 comments
Closed

Provide a start script for a setup based on nixpkgs #784

Profpatsch opened this issue Mar 27, 2019 · 2 comments
Labels
P1 critical: next release type: feature request

Comments

@Profpatsch
Copy link
Contributor

After we implement #604, users on NixOS might have a hard time setting up a basic example without rules_nixpkgs support. We should provide a second start script (/start-nixpkgs), or make the start script ask interactively.
@mboes
Copy link
Member

mboes commented Mar 28, 2019

Or auto-detect NixOS.

Profpatsch added a commit that referenced this issue Apr 1, 2019
@Profpatsch
Move start script from nixpkgs to bindists
6237cff 
We want to make it easy to new users. We can’t assume most users have
nix installed, so we default to the bindists.

We should also provide auto-detection of nix and generate a nixpkgs
script in that case. Tracking issue:
#784

Closes: #604
Profpatsch added a commit that referenced this issue Apr 1, 2019
@Profpatsch
Move start script from nixpkgs to bindists
0aeca68 
We want to make it easy to new users. We can’t assume most users have
nix installed, so we default to the bindists.

We should also provide auto-detection of nix and generate a nixpkgs
script in that case. Tracking issue:
#784

Closes: #604
Profpatsch added a commit that referenced this issue Apr 2, 2019
@Profpatsch
Move start script from nixpkgs to bindists
1c12e8f 
We want to make it easy to new users. We can’t assume most users have
nix installed, so we default to the bindists.

We should also provide auto-detection of nix and generate a nixpkgs
script in that case. Tracking issue:
#784

Closes: #604
Profpatsch added a commit that referenced this issue Apr 2, 2019
@Profpatsch
Move start script from nixpkgs to bindists
1fcd3c1 
We want to make it easy to new users. We can’t assume most users have
nix installed, so we default to the bindists.

We should also provide auto-detection of nix and generate a nixpkgs
script in that case. Tracking issue:
#784

Closes: #604
@Profpatsch Profpatsch mentioned this issue May 2, 2019
Closed
@Profpatsch
Copy link
Contributor Author

Apparently we forgot about OSX, which also only works with the nix backend, see #855.

In #855 (comment) I give an example of a working WORKSPACE file. Trying to get it to run with rules_haskell 0.8 is completely hopeless.

@Profpatsch Profpatsch added the P1 critical: next release label May 2, 2019
@Profpatsch Profpatsch mentioned this issue Jul 9, 2019
Closed
Profpatsch added a commit that referenced this issue Jul 30, 2019
@Profpatsch
start: add ability to create a nixpkgs-based workspace
791d7bc 
When we switched the default to bindists, we lost the ability to
generate a nixpkgs-based workspace with the `start` script.

`start` has two options now, `--use-nix` and `--use-bindists`.

Closes: #784
Profpatsch added a commit that referenced this issue Sep 2, 2019
@Profpatsch
start: add ability to create a nixpkgs-based workspace
5ea6b0b 
When we switched the default to bindists, we lost the ability to
generate a nixpkgs-based workspace with the `start` script.

`start` has two options now, `--use-nix` and `--use-bindists`.

Closes: #784
Profpatsch added a commit that referenced this issue Sep 9, 2019
@Profpatsch
start: add ability to create a nixpkgs-based workspace
9abe071 
When we switched the default to bindists, we lost the ability to
generate a nixpkgs-based workspace with the `start` script.

`start` has two options now, `--use-nix` and `--use-bindists`.

Closes: #784
@mergify mergify bot closed this as completed in 9b7eac9 Sep 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
P1 critical: next release type: feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mboes @Profpatsch