Skip to content
This repository has been archived by the owner on Dec 5, 2022. It is now read-only.

$HOME/.composer should not be a cache bucket #89

Closed
pbuyle opened this issue Mar 4, 2014 · 4 comments
Closed

$HOME/.composer should not be a cache bucket #89

pbuyle opened this issue Mar 4, 2014 · 4 comments
Labels
Milestone

Comments

@pbuyle
Copy link

pbuyle commented Mar 4, 2014

For Composer, vagrant-cachier uses $HOME/.composer as cache bucket. But this folder is not a cache-only folder. Composer store other data in there, such as global configuration ($HOME/.composer/config.json) and globally installed packages ($HOME/.composer/composer.json, $HOME/.composer/vendor and $HOME/.composer/bin).

According to Composer documentation (see https://getcomposer.org/doc/03-cli.md#composer-cache-dir), the folder to use as cache bucket should be $HOME/.composer/cache.

@fgrehm
Copy link
Owner

fgrehm commented Mar 4, 2014

No worries, I'll try to have a look at that

/cc @fh

@fh
Copy link
Contributor

fh commented Mar 4, 2014

Good point, @pbuyle is correct here. (Though I personally like having the global composer.json shared as well, but that is obviously not sth everyone wants).

@fgrehm Are you going to tackle this one, or should I?

@fgrehm fgrehm added this to the v0.6.1 milestone Mar 5, 2014
@fgrehm fgrehm added the bug label Mar 5, 2014
@fgrehm
Copy link
Owner

fgrehm commented Mar 5, 2014

@fh be my guest :-) I'll /cc you in case I end up fixing it.

I'm scheduling this for 0.6.1 and I've tagged it as a bug

@fgrehm fgrehm modified the milestones: v1.0, v0.6.1 Mar 25, 2014
@fgrehm fgrehm closed this as completed in c4db3c1 Jul 21, 2014
@fgrehm
Copy link
Owner

fgrehm commented Jul 21, 2014

This was fixed in git, a new release will come out with it as soon as I'm done with the stuff tagged with the v1.0.0 milestone

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants