Visitar URL original
Tracking ticket for Galois `new-build` requirements · Issue #3577 · haskell/cabal · GitHub
Skip to content

Tracking ticket for Galois new-build requirements #3577

Open

Description

@acfoltzer

I've been gathering assessments and feedback about the new-build features from my colleagues here at Galois. This ticket tracks the issues that we've found are particularly relevant for us, and that would need to be resolved before we can adopt new-build for most of our projects.

This is not meant to be exhaustive, or meant to imply that other issues are not important; this is just a scratchpad that'll evolve as I gather more feedback. Usernames in parentheses are the owners of this particular ticket from the Galois side, even when that's different from the assignee.

Must resolve

These are the features that currently prevent us from adopting new-build on one or more projects:

Nice to resolve

Not showstoppers, but necessary to make it worth switching from an existing system:

Bonus

Not necessarily specific new-build, but would be of great utility for adopters if we'll already be working in the neighborhood:

Activity

  1. 23Skidoo commented on Jul 21, 2016

    @23Skidoo
    Member
  2. ezyang commented on Jul 21, 2016

    @ezyang
    Contributor

    @acfoltzer I posted work arounds for #3473 and #3535 and a work plan for #3417.

  3. dcoutts commented on Jul 24, 2016

    @dcoutts
    Contributor

    @acfoltzer this is very useful to help prioritise, thanks for taking the time to try it out.

  4. hvr commented on Jul 25, 2016

    @hvr
    Member

    @acfoltzer Just wondering, do you really not miss/need new-test/new-bench/new-run? :-)

  5. acfoltzer commented on Jul 25, 2016

    @acfoltzer
    CollaboratorAuthor

    @dcoutts: glad it's helpful, it is for us as well!

    @hvr: ha, what an omission! Is there an issue for those yet? Some of the feedback in my inbox this morning has some ideas about particular interfaces for these, so I'd like to get that written up.

  6. hvr commented on Jul 26, 2016

    @hvr
    Member

    @acfoltzer I couldn't find one, please create one or more issues to dump your ideas there! :-)

  7. dcoutts commented on Jul 29, 2016

    @dcoutts
    Contributor

    Note to self: write up ticket on locking in the store to allow concurrent installs without corrupting the store.

    Update: #3741

  8. dcoutts commented on Sep 24, 2016

    @dcoutts
    Contributor

    @aisamanra btw if you're hacking on things, you're very welcome to join #hackage and chat with us.

  9. dagit commented on Nov 19, 2016

    @dagit
    Collaborator

    Looks like we also need: #4120

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    cabal-install: v2-build systemAffecting v2-build and related commands that use v2-architecture (aka "nix local builds").meta: tracking

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions