[aur-general] Move vagrant and ceph to [community]?
danielwallace at gtmanfred.com
Wed Mar 5 18:49:11 EST 2014
Did anyone step up for ceph? I have been messing with that and was working on adding modules and states to salt. If no one has stepped up I will look into moving it this weekend probably.
Sent via the Samsung GALAXY S®4, an AT&T 4G LTE smartphone
-------- Original message --------
From: Jonathan Steel <mail at jsteel.org>
Date:03/05/2014 3:10 PM (GMT-06:00)
To: "Discussion about the Arch User Repository (AUR)" <aur-general at archlinux.org>
Subject: Re: [aur-general] Move vagrant and ceph to [community]?
On Wed 05 Mar 2014 at 20:21, Jonathan Steel wrote:
> On Wed 05 Mar 2014 at 11:29, Ido Rosen wrote:
> > [...]
> > Note that for vagrant, you really should use vagrant-installers,
> > rather than using gems/bundler directly for it, if you're going to
> > create a package. Maybe the right way is to add support to
> > vagrant-installers for PKGBUILDs.
> > [...]
> I have started looking at the best way to package it. I'll propose my
> changes to you once I'm happy with it and if you would be happy to maintain
> it in the AUR for a little time (or I could take over it) to allow people
> to test the changes before moving it to [community] I think that would be
What's your opinion on how the packages ruby-vagrant and vagrant-git do it?
Before I even looked at those, that's the approach I was going for.
More information about the aur-general