-
Notifications
You must be signed in to change notification settings - Fork 19
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
Create app-target for each executable cabal package #36
Comments
@roberth @HariAmoor-professional Why do we need this? |
I think it's relevant for multi-executable packages and packages whose executable has a different name than the package name. |
How do we approach this?
|
A regex on the cabal file contents may actually go a long way.
We shouldn't do IFD to evaluate |
Yea, we should parse the What should the interface be? In the context of #62, to begin with I think we could add an option under EDIT: Or we can put this in the |
Putting it in That shouldn't stop us from also adding information from passthru, although perhaps consistency with the rest of the ecosystem is a reason to make such improvements in cabal2nix instead.
Here everything except |
So, let's go with the So maybe (for future expansion): Do we still need a separate {
outputs.localPackages = {
foo = {
package = <the drv>;
exes.foo-exe = <the app>;
};
};
} |
Good points, and doing it all merged in I confused |
We can do it as part of this change (#137). It would also be consistent with the |
This ticket corresponds to @roberth's comment on #34. To restate, we need to create a flake output in
apps'.*
for each executable cabal package. The logic to filter executable packages from non-executable ones is non-trivial.The text was updated successfully, but these errors were encountered: