[EPEL-devel] Re: Proposed Package: flatpak as rpm (far) updater (faru)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Nov 9, 2024 at 7:49 AM Troy Dawson <tdawson@xxxxxxxxxx> wrote:
Flatpaks are the new wave of installing desktop packages.  Both GNOME and KDE graphical install/update programs work with flatpaks.
But what about dnf/yum?

I would really like to install, and update, my flatpaks the same as I do rpms.

FAR
These are the packages that you would see in epel.  They would be in the format:
  flatpak-<package>-<repo>
  flatpak-firefox-fedora
On installation, they would ensure that the flatpak remote repo is added, and then install the package globally via flatpak.
On removal, it would remove the globally installed package via flatpak.

FARU
A bit more complicated, but very do-able.
faru would create it's own local dnf repo, as well as add the faru dnf config pointing at that local dnf repo.
At regular intervals (daily?) it would look at the global flatpak packages installed.  If there isn't a far for them, it will create one.  It then looks at the remote package versions to see if there is an update.  If there is an update, it will create a new far, and put it in it's repo.

Then, whenever the machine updates it's rpms, it will update it's flatpaks as well.

What do people think?
I'd like both positive and negative feedback.  But I'd also like explanations/reasons for all feedback.

Troy
p.s. No, I haven't done anything other than in my head.  I would be surprised if I was the only one to think of this, so I'm expecting someone to point me to a similar project that I didn't see.

One thing I found out is that you can set your machine to automatically update flatpaks.
So FARU isn't really needed.  Plus, it was rather complex.
But I still like the idea of using and rpm to install and uninstall a flatpak.

Troy
 
-- 
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux