fabulousleft.blogg.se

Aria2 scriptlist
Aria2 scriptlist











  1. #Aria2 scriptlist how to
  2. #Aria2 scriptlist install
  3. #Aria2 scriptlist software

#Aria2 scriptlist install

With this setup, you can finally install programs from flatpak in a template to provide it to other qubes, with bells and whistles to not have to worry about creating desktop files or keeping them up to date.

aria2 scriptlist

#Aria2 scriptlist how to

This could be enhanced by asking the user if they want to update or skip for later, but I still have to figure how to make notify-send from the root user, I opened a Qubes OS issue about this. This solution will look for flatpak programs updates each time the template starts, which should occur regularly to update the template packages, and update them unconditionnaly. # start monitoring flatpak changes to reload icons Start the file monitoring script at boot §įinally, you need to activate the script created above when the templates boots, this can be done by adding this snippet to /rw/config/rc.local: You have to mark this file as executable with chmod +x /usr/local/sbin/sync-app.sh.ģ.3. etc/qubes/post-install.d/10-qubes-core-agent-appmenus.sh var/lib/flatpak/exports/share/applications/ |įind /var/lib/flatpak/exports/share/applications/ -type l -name "*.desktop" | while read lineįind /usr/share/applications/ -xtype l -delete # - remove outdated entries of programs that were removed

aria2 scriptlist

Here is a script to automatically keep the applications list in sync every time a change is made to the flatpak applications.įor the setup to work, you will have to install the package inotify-tools in the template, this will be used to monitor changes in a flatpak directory.

#Aria2 scriptlist software

If you install or remove flatpak programs, either from the command line or with the Software application, you certainly want them to be easily available to add in the qubes menus. Restart the template, GNOME software is now able to install flatpak programs! GNOME Software gitlab issue #2336 saying a default route is required to make it work In order to circumvent a GNOME Software bug, if you want to use it to install packages (Flatpak or not), you need to add the following line to /rw/config/rc.local: Mkdir -p /home/user/.config/environment.d/Ĭat /home/user/.config/environment.d/nf Make the environment variable persistent for the user user, this will allow GNOME Software to work with flatpak and all flatpak commands line to automatically pick the proxy. In order to add Flathub repository, you need to define the variable https_proxy so flatpak can figure how to reach the repository through the proxy:įlatpak remote-add -if-not-exists flathub Setup §Īll the commands in this guide are meant to be run in a Fedora or Debian template as root. I really like flatpak as it provides extra security features and a lot of software choice, and all the data created by Flatpak packaged software are compartmentalized into their own tree in ~/.var/app//.įlathub: main flatpak repository 2. Today, I'll explain how to install programs from Flatpak in a template to provide to other qubes. I recently wanted to improve Qubes OS accessibility to new users a bit, yesterday I found why GNOME Software wasn't working in the offline templates.













Aria2 scriptlist