I am investigating whether there is a quick fix to update the TAILS distribution build system to continue using Vagrant.
(see https://labs.riseup.net/code/issues/8086 ) It currently uses a rake to invoke Vagrant::Environment, but this *seemingly* only works with now ancient versions of Vagrant. I am fairly new to ruby and rake, gems and rvm This post <https://mailman.boum.org/pipermail/tails-dev/2014-July/006258.html> suggests this is impossible to do with, say, the RPM or Deb version supplied on the current Vagrant site rather than older version gems. I have tried various methods to learn about ruby paths and inserting new require paths into the Rakefile explicitly, but would *very much appreciate* pointers or advice over this issue to save time and keep the TAILS devs using Vagrant as their tool of choice! Ad*Thanks*vance -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/7d89b910-85be-4f2c-b960-b3c2e4f166e5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
