[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:
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
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 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:
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 best. [...]
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