-
Notifications
You must be signed in to change notification settings - Fork 842
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
Install packages to the snapshot database with profiling when they are present in the global database without profiling #124
Comments
Researching the GHC-specific details for this (and relatedly #127):
I confirm that the global version doesn't have profiling:
So in getting the package list in And then we can see the snapshot one does have profiling:
(Note: they both have the same package ID, so if we wanted to, it seems impossible to distinguish them.) But seeing as we didn't touch the global database to remove the offending version, and in fact in reality in this scenario I actually installed data-class-default to the global database afterwards (so it is the latest), we should confirm that we're able to use the older snapshot one: Just global:
With snapshot db:
So GHC chooses the packages based on the ordering of |
@DanBurton Confirm fixed on master? |
It appears that profiling libraries are no longer installed by default. I presume this is by design?
I installed a non-profiling version of data-default-class into my global package database. (Strangely, Note that data-default-class is not present in the snapshot package-db.
I have a trivial file that pretends to depend on cookie.
Now when we try to compile with profiling
So
This worked. (Yay!)
|
Example: The
data-default-class
package is installed in the global database without profiling. My project depends on thecookie
package, but when stack tries to install it with profiling into a snapshot database, it ends in failure:See #120 for details.
The text was updated successfully, but these errors were encountered: