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

Tracking ticket for Galois `new-build` requirements #3577

Open
acfoltzer opened this Issue Jul 21, 2016 · 9 comments

Comments

Projects
None yet
6 participants
@acfoltzer
Collaborator

acfoltzer commented Jul 21, 2016

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:

  • #3417: Dependency executables aren't in PATH
  • #3586: Support --prefix, --datadir, etc
  • #3535: How do I haddock with new-build?
  • #3638: (@dmwit)
    • new-run
    • new-test
    • new-bench
    • new-exec
  • #4120: data files for inplace builds

Nice to resolve

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

  • #2189: Support non-Hackage dependencies
  • #3332: new-install interface for installing executables (@dmwit)
    • nonlocal
    • local
  • #3333: Garbage collecting the store (@dmwit)
  • #3391: Add flag to build all packages in project with new-build
  • #3394: new-build silent failure on zip-archive-0.3.0.2
  • #3473: Replacement needed for cabal copy
  • #3585: Add flag to new-configure for adding extra packages to cabal.project.local (@aisamanra)
  • #3587: Allow specifying freeze file for other commands

Bonus

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

  • #1493: build Setup.hs with local compiler when cross-compiling (@Ericson2314 laying the groundwork)
@23Skidoo

This comment has been minimized.

Member

23Skidoo commented Jul 21, 2016

/cc @dcoutts

@ezyang

This comment has been minimized.

Contributor

ezyang commented Jul 21, 2016

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

@dcoutts

This comment has been minimized.

Member

dcoutts commented Jul 24, 2016

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

@hvr

This comment has been minimized.

Member

hvr commented Jul 25, 2016

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

@acfoltzer

This comment has been minimized.

Collaborator

acfoltzer commented Jul 25, 2016

@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.

@hvr

This comment has been minimized.

Member

hvr commented Jul 26, 2016

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

@dcoutts

This comment has been minimized.

Member

dcoutts commented Jul 29, 2016

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

Update: #3741

@dcoutts

This comment has been minimized.

Member

dcoutts commented Sep 24, 2016

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

@dagit

This comment has been minimized.

Collaborator

dagit commented Nov 19, 2016

Looks like we also need: #4120

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