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

Turn no-exe on by default #103

Closed
alerque opened this issue Dec 10, 2016 · 6 comments

Comments

Projects
None yet
4 participants
@alerque
Copy link

commented Dec 10, 2016

I've just run into an upgrade to a haskell program (pandoc) requiring a new version on this. The latest version seems to have introduced some new binaries. Of course these conflict with existing binaries of the same name from the popular remarshal project which also offers other formats.

I see there is a no-exe flag but it is disabled causing upstream packages to have this start showing up without much warning and with no resolution. I need the features remarshal offers and my scripts expect it's command line syntax. I only need the haskel library part of this as a dependency.

Further I don't see what sense it makes to package these together. Could the x2y binaries not just as well be packaged separately? What happens when the haskell-json package introduces a json2yaml binary too? Why does having it in this package make any more sense? At the very least something unique in the binary names would be appreciated.

@alerque alerque changed the title Turn no-exe Turn no-exe on by default Dec 10, 2016

@snoyberg

This comment has been minimized.

Copy link
Owner

commented Dec 12, 2016

Let me guess: you're building with cabal and the executables are ending up in ~/.cabal/bin?

@alerque

This comment has been minimized.

Copy link
Author

commented Dec 12, 2016

No. I'm actually using the Arch Linux package in the haskell-core repository and the package has file conflicts with remarshal because both put things in /usr/bin. I suppose this might not even be the right place to file this, I need to find who is choosing packaging options or those builds.

@snoyberg

This comment has been minimized.

Copy link
Owner

commented Dec 12, 2016

That's probably the correct place, standard Haskell build tooling does not specify installing executables into any global location.

@kanishka-azimi

This comment has been minimized.

Copy link

commented May 4, 2017

Might help - https://www.archlinux.org/packages/community/x86_64/haskell-yaml/ , https://wiki.archlinux.org/index.php/Haskell_package_guidelines sounds like the default is to bundle libraries and exes together in one Arch package. Other distros might have more complex default policies that Arch Haskell package maintainers could model their policy after?

I would close the issue here and reopen if you hit a roadblock with Arch maintainers? (I am just an outsider observer, I do not maintain this package.)

@sol

This comment has been minimized.

Copy link
Collaborator

commented Mar 19, 2018

Personally, I would be in favor of either defaulting the no-exe flag to True or removing the executables from the package.

@snoyberg

This comment has been minimized.

Copy link
Owner

commented Mar 21, 2018

I agree, I'll make that change shortly.

@snoyberg snoyberg closed this in 60241cb Mar 21, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.