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 attenti
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
On Tue 11 Mar 2014 at 19:48, Jonathan Steel wrote:
> On Fri 21 Feb 2014 at 19:34, Jonathan Steel 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
* Jonathan Steel [2014-03-11 19:48:41 +]:
> Vagrant has been updated in the AUR using my proposed installation method
> (not using the rpm file). This means needing 22 ruby-* packages.
>
> Please share comments/suggestions/concerns either here or in the comments:
>
> https://aur.archlinux.or
On Fri 21 Feb 2014 at 19:34, Jonathan Steel 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 co
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 wrote:
> On Fri 21 Feb 2014 at 12:51, Ido Rosen 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 vagra
Also, the source repo for vagrant itself is
https://github.com/mitchellh/vagrant ... but I think the RPMs and other
packaging is generated by https://github.com/mitchellh/vagrant-installers
On Fri, Feb 21, 2014 at 1:32 PM, Ido Rosen wrote:
> The official distribution is the RPM/DEB/binary distr
The official distribution is the RPM/DEB/binary distribution. The
ruby-vagrant package is different - I don't believe it is based on
vagrant-installers. If we wanted to not use the RPMs (which are very
self-contained) but still have a low-maintenance way of packaging this, we
could start here: ht
Hi
On Fri, Feb 21, 2014 at 9:51 AM, 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 mo
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
wi
11 matches
Mail list logo
