[aur-general] Move vagrant and ceph to [community]?
Massimiliano Torromeo and/or Jonathan Steel: Just following up to your previous posts below. 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. For ceph, it's a pretty typical conf/make/install. A lot of customization/flexibility should be left for the user in the ceph case, and adding a wiki page would be a good idea as well. Ceph stable releases are approx. every 3 months, so it is predictable and relatively low-maintenance, whereas Vagrant has more bursty releases. If you take ceph, you will probably find it useful to adopt ceph-git in AUR as well. Cheers, Ido On Fri Feb 21 17:20:39 EST 2014, Massimiliano Torromeo <massimiliano.torromeo@gmail.com> wrote:
On Wed 05 Mar 2014 at 11:29, Ido Rosen wrote:
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 best. In future please reply inline and to the original thread. Thanks, -- Jonathan Steel
On Wed 05 Mar 2014 at 20:21, Jonathan Steel wrote:
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. -- Jonathan Steel
participants (2)
-
Ido Rosen
-
Jonathan Steel