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

Streamline package options #587

Closed
12 tasks done
agross opened this issue Feb 8, 2015 · 4 comments
Closed
12 tasks done

Streamline package options #587

agross opened this issue Feb 8, 2015 · 4 comments

Comments

@agross
Copy link
Contributor

agross commented Feb 8, 2015

Paket supports several options, configured at different levels:

  • content: none (global)
  • framework (for nuget in paket.dependencies)
  • copy_local (paket.references)

I think we should streamline these to let the user define any option on any level (global, package level, reference level) with the possibility to enhance the option set or override default options on lower levels (comparable to Git's three-level configuration system).

The syntax should be streamlined to the one discussed here.

paket.dependencies:

copy_local: true
framework: >= net40
content: none

nuget Foobar 1.2.3 copy_local: true, framework: >= net40, content: none

paket.references:

Foobar copy_local: true, framework: >= net40, content: none

Current status

paket.dependencies global support:

  • content
  • framework
  • copy_local
  • import_targets

paket.dependencies per-package support:

  • content
  • framework
  • copy_local
  • import_targets

paket.references support (only per-package):

  • content
  • framework
  • copy_local
  • import_targets
@forki
Copy link
Member

forki commented Feb 17, 2015

The same applies to import_targets:false which already works in paket.references files.

@agross
Copy link
Contributor Author

agross commented Feb 17, 2015

Please check off above ;-)

forki added a commit that referenced this issue Feb 17, 2015
forki added a commit that referenced this issue Feb 18, 2015
forki added a commit that referenced this issue Feb 18, 2015
forki added a commit that referenced this issue Feb 18, 2015
forki added a commit that referenced this issue Feb 18, 2015
forki added a commit that referenced this issue Feb 18, 2015
@forki
Copy link
Member

forki commented Feb 18, 2015

free

@agross
Copy link
Contributor Author

agross commented Mar 20, 2015

Perhaps we should add redirects: on as well?

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

No branches or pull requests

2 participants