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

We have binding redirects for nunit in Paket console application #806

Closed
theimowski opened this issue May 1, 2015 · 4 comments
Closed

Comments

@theimowski
Copy link
Member

while we don't have them for Paket.Tests project - does the --redirects option for paket install handle different packages in different projects?

/cc @isaacabraham

@isaacabraham
Copy link
Contributor

It is pretty crude, as far as I remember it just supplies the redirects for all packages across all projects. Even if the project doesn't use a specific redirect (this is harmless though).

However, if there is no config file in the tests project you must create one first - the BR code won't do that automatically.


From: Tomasz Heimowskimailto:[email protected]
Sent: ‎01/‎05/‎2015 08:29
To: fsprojects/Paketmailto:[email protected]
Cc: Isaac Abrahammailto:[email protected]
Subject: [Paket] We have binding redirects for nunit in Paket console application (#806)

while we don't have them for Paket.Tests project - does the --redirects option for paket install handle different packages in different projects?

/cc @isaacabraham


Reply to this email directly or view it on GitHub:
#806

@theimowski
Copy link
Member Author

I see, maybe we could, as an enhancement, create new app.config file, as well as limit the redirects to the ones referenced by project only?

@isaacabraham
Copy link
Contributor

yes, could do both - can you create issues for both of them?

The first one does make me think though how we would identify this though e.g. create .config for every .csproj / .vbproj / .fsproj? Only exes? websites? etc. etc.?

The second one is definitely doable, probably just a bit of work to expand the current code to supply a different set of BRs for each project.

@theimowski
Copy link
Member Author

ok closing this in favor of the new ones

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