-
Notifications
You must be signed in to change notification settings - Fork 696
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
Remove support for .zip
format source distributions
#5735
Comments
+1. I can see how .zip makes sense for distributing Windows binaries (Windows Explorer supports it natively), but for source packages it makes more sense to have a single standard format. |
👍 EDIT I thought |
Agreed. |
hvr
changed the title
RFC: Remove support for
Remove support for Nov 27, 2018
.zip
format source distributions.zip
format source distributions
5 tasks
Finished as of #5755 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
cabal sdist
has had support for generating.zip
ped source distributions ever since it was added in ae0dee3The original implementation relied on invoking an external
zip
executable, whereas in the course of thenew-sdist
implementation this the Haskell libraryzip-archive
was used (see 8fe7607) thereby gaining an additional dependency.However, it's not clear to me if this feature is even relevant to anyone anymore; This feature is also rather asymmetric as there's only write support but not read support for
.zip
sdists. I'd argue it'd be more in line w/ the KISS principle to handle this by a simpletgz2zip
utility than to bloatcabal
with trivial convenience concerns which lead to feature creep.If nobody needs/uses this feature it'd be effectively dead-code and we should eliminate it in the interest of reducing current and future maintenance costs of additional code-paths as well as an additional library dependency.
Concretely, I suggest to
--zip
feature (and associated codepaths) fromsdist
&v2-sdist
,zip-archive
dependency, andtar2zip
ortgz2zip
tool and host its package on Hackage to satisfy the needs of what I believe to be a very small minority target audience :-)The text was updated successfully, but these errors were encountered: