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.

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

Support alternate ways of referring to packages in build-deps #2271

Closed
bitemyapp opened this issue Dec 13, 2014 · 2 comments
Closed

Support alternate ways of referring to packages in build-deps #2271

bitemyapp opened this issue Dec 13, 2014 · 2 comments

Comments

@bitemyapp
Copy link
Contributor

So that private packages are easier to work on.

With this thread in mind: https://twitter.com/Blaisorblade/status/543572310113153024

Does anyone have any ideas of what might be a nice way to better support users of Haskell on projects with private dependencies? git submodules and cabal sandbox add-source is too manual / script-y.

@23Skidoo
Copy link
Member

Duplicate of #2189.

@23Skidoo
Copy link
Member

git submodules and cabal sandbox add-source is too manual / script-y.

I think the situation could be improved by

  1. Moving to a package tree-centric model (No package is an island #1367).
  2. Adding a --pkgroot argument to add-source (or something like it) so that you could run a single command to add-source all dependencies from the current tree.
  3. Fixing misc. usability issues with add-source deps (only reinstall the deps that the current package actually depends on, don't reinstall everything again when a single package failed, anything else I forgotten).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants