Consider deprecation

[patcon]

Hey! This seems like an awesome plugin, but there's another one that seems to have a more elegant solution:
https://github.com/fgrehm/vagrant-cachier

I don't suppose you might consider deprecating yours in favour of contributing to that project? I've brought up a similar suggestion in the queues for vagrant-rvm-cache: maljub01/vagrant-rvm-cache#1

Just thinking it would be awesome if we all rallied around a common project :)

cc: @fgrehm

[avit]

Yup, agree. Mine is currently incompatible with the new Vagrant plugin architecture anyway.

I'll put a notice up on the README.

[patcon]

Rockin man. Thanks for hearing me out :)

Any thoughts on actually yanking it so that there's one less deprecated plugin in the gem list -r vagrant- output?

[avit]

Yes, eventually, but if people are using it I don't want to just yank it. Probably the best course of action is to release an update with a deprecation warning so people are aware that it will go away someday.

[patcon]

From http://help.rubygems.org/kb/gemcutter/removing-a-published-rubygem

Running gem yank will remove your gem from being available with gem install and the other gem commands. We keep the gem available for download still for two main reasons:

So it doesn't actually prevent anyone from using it if they already are (via bundler), it just prevents new people from finding it. Anyhow, absolutely your call -- just wanted to clarify

[patcon]

Or hey, this guy brought up a good point:
https://twitter.com/thegcat/status/342323856574394368

Maybe the more elegant solution is a final release with a big obvious deprecation warning and pointer to vagrant-cachier if vagrant 1.1+ is detected?