In this article, https://www.zdnet.com/article/kali-linux-for-vagrant-hands-on/ the author notes:
"I didn't find Vagrant on Fedora, but there are several articles in the Fedora Developer Portal which describe installing and using it."
Actually, vagrant definitely *is* in Fedora; it's just not a GUI app so it doesn't show up in a search in Software. How can we either
1. Make vagrant available in software, or
2. Make it obvious to people searching in Software that this is an available command line tool?
On Wed, Oct 17, 2018 at 3:09 AM Matthew Miller mattdm@fedoraproject.org wrote:
In this article, https://www.zdnet.com/article/kali-linux-for-vagrant-hands-on/ the author notes:
"I didn't find Vagrant on Fedora, but there are several articles in the Fedora Developer Portal which describe installing and using it."
Actually, vagrant definitely *is* in Fedora; it's just not a GUI app so it doesn't show up in a search in Software. How can we either
Make vagrant available in software, or
Make it obvious to people searching in Software that this is an
available command line tool?
They even link here: https://developer.fedoraproject.org/tools/vagrant/vagrant-virtualbox.html
which clearly states "sudo dnf install vagrant".
So I think the author was just lazy trying out the command.
OTOH, it would be nice if gnome-software could somehow inform the user that it contains only graphical apps.
On Wed, Oct 17, 2018 at 10:33:38AM +0200, Kamil Paral wrote:
They even link here: https://developer.fedoraproject.org/tools/vagrant/vagrant-virtualbox.html which clearly states "sudo dnf install vagrant". So I think the author was just lazy trying out the command.
I don't think that's the case. This is a pretty consistently Fedora-friendly author, and it's not super-clear if you're not deep into how things work that instructions on that page give you software actually from the Fedora Project.
On Wed, Oct 17, 2018 at 3:30 PM Matthew Miller mattdm@fedoraproject.org wrote:
On Wed, Oct 17, 2018 at 10:33:38AM +0200, Kamil Paral wrote:
They even link here:
https://developer.fedoraproject.org/tools/vagrant/vagrant-virtualbox.html
which clearly states "sudo dnf install vagrant". So I think the author was just lazy trying out the command.
I don't think that's the case. This is a pretty consistently Fedora-friendly author, and it's not super-clear if you're not deep into how things work that instructions on that page give you software actually from the Fedora Project.
OK. Vagrant is also not visible in Ubuntu's Software Center, though. So this is likely a case where the author recognizes an apt command, but doesn't recognize a dnf command.
On Wed, 17 Oct 2018 at 02:09, Matthew Miller mattdm@fedoraproject.org wrote:
- Make vagrant available in software, or
You can make random packages show up in software, although I think only codecs and fonts use this feature. To do it, just write a .metainfo.xml file (compnent type "generic"), and install it into /usr/share/metainfo -- although you'll need to also include an icon (which can be remote, e.g. https://foo.bar/baz.png), a screenshot and a (hopefully) translated name and long description.
Richard.
On Tue, Oct 16, 2018, at 9:08 PM, Matthew Miller wrote:
In this article, https://www.zdnet.com/article/kali-linux-for-vagrant-hands-on/ the author notes:
"I didn't find Vagrant on Fedora, but there are several articles in the Fedora Developer Portal which describe installing and using it."
Actually, vagrant definitely *is* in Fedora; it's just not a GUI app so it doesn't show up in a search in Software.
What I do is `yum install vagrant` inside my development container: https://github.com/cgwalters/sysmgmt-personal/blob/0e517cf8e4d67915f909989e9... I bind mount in the /run/libvirt/libvirt-sock so that it can access the host libvirtd.
This keeps my host smaller and aids flexibility; if I want to test a different version of Vagrant that's just a different container, etc.
Just commenting on this as my mission isn't done until we've moved the default user experience to containers; changes to encourage people to install software directly on their host go counter to this.
On Thu, Oct 18, 2018 at 01:26:16PM -0400, Colin Walters wrote:
What I do is `yum install vagrant` inside my development container: https://github.com/cgwalters/sysmgmt-personal/blob/0e517cf8e4d67915f909989e9... I bind mount in the /run/libvirt/libvirt-sock so that it can access the host libvirtd.
This keeps my host smaller and aids flexibility; if I want to test a different version of Vagrant that's just a different container, etc.
Just commenting on this as my mission isn't done until we've moved the default user experience to containers; changes to encourage people to install software directly on their host go counter to this.
Okay, that's fair. We've talked about having a pet container as the default shell on Silverblue. We should definitely include /run/libvirt/libvirt-sock as part of that. Possibly crazy idea: some way for Software to help manage installation of software into that container.
desktop@lists.fedoraproject.org
-
Colin Walters -
Kamil Paral -
Matthew Miller -
Richard Hughes