-
-
Notifications
You must be signed in to change notification settings - Fork 153
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
Set meta.mainProgram
#541
Comments
13 tasks
sternenseemann
added a commit
to NixOS/distribution-nixpkgs
that referenced
this issue
May 7, 2022
sternenseemann
added a commit
to NixOS/distribution-nixpkgs
that referenced
this issue
May 7, 2022
sternenseemann
added a commit
to sternenseemann/cabal2nix
that referenced
this issue
May 8, 2022
If a there is a single executable, it is obviously the mainProgram. We'll see a lot of example binaries this way, of course, but these being built is not exactly a new problem. Fixes: NixOS#541
sternenseemann
added a commit
to sternenseemann/distribution-nixpkgs
that referenced
this issue
May 9, 2022
sternenseemann
added a commit
to NixOS/distribution-nixpkgs
that referenced
this issue
May 19, 2022
sternenseemann
added a commit
to NixOS/distribution-nixpkgs
that referenced
this issue
May 19, 2022
Upstream haskellPackages.mkDerivation supports this since NixOS/nixpkgs#129093 / 06fb9a9. Reference: NixOS/cabal2nix#541
First step is done and ready for review: NixOS/distribution-nixpkgs#20 |
sternenseemann
added a commit
to NixOS/distribution-nixpkgs
that referenced
this issue
May 22, 2022
Upstream haskellPackages.mkDerivation supports this since NixOS/nixpkgs#129093 / 06fb9a9. Reference: NixOS/cabal2nix#541
sternenseemann
added a commit
to sternenseemann/cabal2nix
that referenced
this issue
May 28, 2022
If a there is a single executable, it is obviously the mainProgram. We'll see a lot of example binaries this way, of course, but these being built is not exactly a new problem. Fixes: NixOS#541
sternenseemann
added a commit
that referenced
this issue
May 28, 2022
If a there is a single executable, it is obviously the mainProgram. We'll see a lot of example binaries this way, of course, but these being built is not exactly a new problem. Fixes: #541
sternenseemann
added a commit
that referenced
this issue
May 28, 2022
If a there is a single executable, it is obviously the mainProgram. We'll see a lot of example binaries this way, of course, but these being built is not exactly a new problem. Fixes: #541
sternenseemann
added a commit
that referenced
this issue
May 28, 2022
If a there is a single executable, it is obviously the mainProgram. We'll see a lot of example binaries this way, of course, but these being built is not exactly a new problem. Fixes: #541
sternenseemann
added a commit
that referenced
this issue
Jun 14, 2022
If a there is a single executable, it is obviously the mainProgram. We'll see a lot of example binaries this way, of course, but these being built is not exactly a new problem. Fixes: #541
sternenseemann
added a commit
that referenced
this issue
Jun 14, 2022
If a there is a single executable, it is obviously the mainProgram. We'll see a lot of example binaries this way, of course, but these being built is not exactly a new problem. Fixes: #541
sternenseemann
added a commit
that referenced
this issue
Jun 14, 2022
If a there is a single executable, it is obviously the mainProgram. We'll see a lot of example binaries this way, of course, but these being built is not exactly a new problem. Fixes: #541
sternenseemann
added a commit
that referenced
this issue
Jul 21, 2022
Upstream haskellPackages.mkDerivation supports this since NixOS/nixpkgs#129093 / 06fb9a9. Reference: #541
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the cabal file has a single executable,
cabal2nix
can generate ameta.mainProgram
attribute, so that the command name can be used by generic code in Nixpkgs.Example use cases:
pkg.exe
shortcut, e.g.${pandoc.exe} --foo
Add exe attribute to packages nixpkgs#158461nix run
needs this info to run the right command when it doesn't match the package nameThe text was updated successfully, but these errors were encountered: