[aur-general] Move vagrant to [community]?

[Jonathan Steel]

On Wed 19 Mar 2014 at 21:45, Jonathan Steel wrote:
> On Mon 17 Mar 2014 at 20:00, Jonathan Steel wrote:
> > On Tue 11 Mar 2014 at 19:48, Jonathan Steel wrote:
> > [...]
> > I plan to move this to [community] in a day or two assuming no further
> > issues are reported.
> 
> It has come to my attention that two plugins are included in vagrant that
> don't fall under the MIT license. These are vagrant-login and
> vagrant-share. Here is the license for those:
> 
> https://gist.github.com/mitchellh/c070cf243b94036bb291
> 
> Are there any objections to providing these proprietary plugins with this
> license?

I've decided to remove these plugins in 1.5.1-5. Users can install them
with:

 % vagrant plugin install vagrant-login
 % vagrant plugin install vagrant-share

... and functionality will be restored, without having to distribute
proprietary software, and this license. 

The plugins will then be stored in ~/.vagrant.d/gems/gems/ (so will be
user-specific) and are not fetched from our servers. I think this is the
best solution for those wanting to use these plugins.

-- 
Jonathan Steel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://mailman.archlinux.org/pipermail/aur-general/attachments/20140320/6319f052/attachment.asc>