Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
haskell-gargantext
haskell-gargantext
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 159
    • Issues 159
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 8
    • Merge Requests 8
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gargantext
  • haskell-gargantexthaskell-gargantext
  • Merge Requests
  • !45

Merged
Opened Jun 22, 2021 by Alp Mestanogullari@amestanogullari
  • Report abuse
Report abuse

make gargantext buildable with stack & cabal in a nix environment

I revamped the whole Nix infrastructure a bit to clearly delineate the bits about providing a suitable environment (with respect to non Haskell deps) and the shell and stack helper expressions, and moved it all under nix/ to make it easier to ignore (if not interested) or focus on (if interested) the Nix infrastructure of this repository.

For some reason, this required changes that don't seem necessary in the Docker environment, even though this all happens using the same GHC version as used in the Docker environment/Stackage LTS snapshot.

The said changes correspond to the source repositories mentioned in the cabal.project and stack.yaml files that have not been left untouched, for which I either pointed to a fork I made, or a different commit that I pushed in a dedicated branch (for the ISCPIF gitlab repositories to which I seemingly have write access).

Many of the changes were about Haddock -- | style syntax being used in an unexpected place, and this was making GHC's parser quite sad.

This commit doesn't (yet?) provide Nix infrastructure for building everything in/through Nix, but shouldn't be too much work with something like haskell.nix, which has suitable tooling to import stack.yaml or cabal.project based project specifications and turn them into fully nixified builds, which might or might not be desirable.

  • Building with stack: stack --nix build
  • Building with cabal: nix-shell nix/shell.nix --run 'cabal build'
Edited Jun 22, 2021 by Alp Mestanogullari

Check out, review, and merge locally

Step 1. Fetch and check out the branch for this merge request

git fetch origin
git checkout -b alp/nix origin/alp/nix

Step 2. Review the changes locally

Step 3. Merge the branch and fix any conflicts that come up

git fetch origin
git checkout origin/dev
git merge --no-ff alp/nix

Step 4. Push the result of the merge to GitLab

git push origin dev

Note that pushing to GitLab requires write access to this repository.

Tip: You can also checkout merge requests locally by following these guidelines.

  • Discussion 1
  • Commits 1
  • Pipelines 1
  • Changes 13
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
0
Labels
None
Assign labels
  • View project labels
Reference: gargantext/haskell-gargantext!45

Revert this commit

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this commit

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.