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

Massimiliano Torromeo massimiliano.torromeo at gmail.com
Fri Feb 21 17:20:39 EST 2014

I would be interested if building from source wouldn't probably mean to
also move a dozen ruby dependencies or use bundler.

I will probably move ceph, which you are also maintaining, though.

On Fri, Feb 21, 2014 at 8:34 PM, Jonathan Steel <mail at jsteel.org> wrote:

> On Fri 21 Feb 2014 at 12:51, Ido Rosen wrote:
> > Hi,
> >
> > I maintain vagrant package in AUR.  I believe vagrant is a very useful
> tool
> > for ArchLinux users.  I am happy to continue maintaining it in AUR;
> > however, for the good of the community, it would be great if one of you
> TUs
> > could move vagrant into [community] as soon as possible so it could get
> > wider exposure.  It currently has ~147 votes.  Releases are infrequent,
> so
> > it has been very easy to maintain overall.
> >
> > AUR package: https://aur.archlinux.org/packages/vagrant/
> > Upstream distribution website: http://www.vagrantup.com/
> >
> > Also, if you'd like to make changes to the PKGBUILD in AUR, you can
> submit
> > a pull request on GitHub: https://github.com/ido/packages-archlinux (under
> > the aur/vagrant directory).
> I use this a bit and was considering moving it to community when I had a
> bit more time. If no one steps up in the next week or so then I'll start
> looking at moving it/the best way to package it.
> --
> Jonathan Steel

More information about the aur-general mailing list