Skip to content

cabal command to remove unused packages #2324

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

Closed
wereHamster opened this issue Jan 5, 2015 · 7 comments
Closed

cabal command to remove unused packages #2324

wereHamster opened this issue Jan 5, 2015 · 7 comments

Comments

@wereHamster
Copy link

Bundler has a subcommand 'clean' which removes all unused gems. This is useful when one upgrades dependencies and wants to get rid of the packages which are afterwards unused.

Building Haskell projects on travis (https://travis-ci.org/) is time consuming because all the dependencies have to be installed afresh for each build. Cabal sandboxes don't help because nothing is preserved between builds. A while ago the travis team added the ability to cache files (1, 2). Travis has builtin support for caching bundler and cocoapod dependencies. Having an equally easy way to enable haskell cache would be useful. However one precondition (according to the travis developers) is that there needs to be an automatic way to clean the cache.

1: http://blog.travis-ci.com/2013-12-05-speed-up-your-builds-cache-your-dependencies/
2: http://docs.travis-ci.com/user/caching/

@ttuegel ttuegel added this to the _|_ milestone Apr 25, 2015
@ttuegel
Copy link
Member

ttuegel commented Apr 25, 2015

This would be addressed by this GSoC proposal.

@wereHamster
Copy link
Author

Was the GSoC proposal accepted?

@23Skidoo
Copy link
Member

Yes, it was.

@peti
Copy link
Collaborator

peti commented Jan 18, 2018

The link from #2324 (comment) points nowhere, unfortunately.

@hvr
Copy link
Member

hvr commented Jan 18, 2018

fwiw, @lspitzner's https://github.com/lspitzner/pkgdbgc tool is currently exploring the design space

@grayjay
Copy link
Collaborator

grayjay commented Jun 11, 2018

Similar issue for new-build: #3333

@jneira
Copy link
Member

jneira commented Mar 26, 2022

i would close this in favour of #3333, v1 commands are deprecated and there is lot of work to be done in v2

@jneira jneira closed this as completed Mar 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants