(address . bug-guix@gnu.org)
CABhyRUitf7CbPZ-S5a_eqqPsA21=27ZutPPw64uj+7jkLDvYhQ@mail.gmail.com
GNU Guix backend for PackageKit / Gnome-Software
- Open
Details
- 4 participants
- Denis 'GNUtoo' Carikli
- Kẏra
- Ludovic Courtès
- Parnikkapore
- Owner
- unassigned
- Submitted by
- Kẏra
- Severity
- wishlist
K
K
(address . 17152@debbugs.gnu.org)
CABhyRUh0caM_mqkPR+diqX1m_WmxkeH4N3ByXaLH2Rs63tsEng@mail.gmail.com
I also filed against PackageKit here:
and gnome-software here: https://bugzilla.gnome.org/show_bug.cgi?id=727367
L
(name . Kẏra)(address . kxra@riseup.net)(address . 17152@debbugs.gnu.org)
87txae3t4q.fsf@gnu.org
Kẏra <kxra@riseup.net> skribis:
Toggle quote (5 lines)
> I also filed against PackageKit here:
> https://bugs.freedesktop.org/show_bug.cgi?id=76810
>
> and gnome-software here: https://bugzilla.gnome.org/show_bug.cgi?id=727367
This is a good idea, but looking at
it seems that PackageKit is not well suited for non-root install systems
and per-user profiles, for instance.
Thanks,
Ludo’.
L
control message for bug #17152
(address . control@debbugs.gnu.org)
87r458uaor.fsf@gnu.org
L
Re: bug#17152:
(name . Kẏra)(address . kxra@riseup.net)(address . 17152@debbugs.gnu.org)
87lh2amt2o.fsf@gnu.org
Hi!
Kẏra <kxra@riseup.net> skribis:
Toggle quote (3 lines)
> I also filed against PackageKit here:
> https://bugs.freedesktop.org/show_bug.cgi?id=76810
FWIW, a Nix back-end has just been merged:
I think a Guix back-end may be simpler, notably because Guix has a
notion of package whereas all Nix sees is derivations, which are
low-level.
The Guix back-end, as I imagine, could essentially embed Guile into
PackageKit and have most of the code written in Scheme. That way it
could trivially use all the support code we have in (guix profiles),
(guix packages), and (gnu packages).
Any takers? :-)
Ludo’.
D
Re: GNU Guix backend for PackageKit / Gnome-Software
(address . 17152@debbugs.gnu.org)
20221208185245.0eb6b800@primary_laptop
Hi,
How does it work when Nix is installed on top of another distribution?
Is there something to handle that in packagekit?
Or with distributions like Ubuntu that also use snap, it is is handled
transparently somehow? Or do users have to choose which package manager
to use?
I wonder that because I'd be interested in somehow supporting the
package manager of a foreign distribution (Parabola) to have an unified
configuration that can work also when guix / guix home is used on top
of another distribution[1].
[1] There are various advantages of using the distribution package
manager instead of guix home in that case, like having the packages
installed system wide for instance, or having the packages take
less space.
Denis.
P
GNU Guix backend for PackageKit / Gnome-Software
(address . 17152@debbugs.gnu.org)
ae3674e904d29801f745cac8c076b7736d1569c6.camel@yahoo.com
(I hope it's OK to bump! 🙂️)
I'm using KDE Neon. In Plasma Discover (which is a PackageKit
frontend), packages from both apt and Flatpak are shown, and you can
pick which way you want to install the package. You can also set a
default.
If a package isn't available on one package manager, that package
manager simply doesn't show up on the list, and pressing "Install" will
simply use another package manager that does have the package.
Flatpak is actually listed twice - once for installing system-wide and
once for installing for the current user only. Only the latter does not
require the equivalent of sudo-ing. So that should point towards a way
to get PackageKit to do non-root installs.
Unfortunately, I couldn't find a way to get pkcon to behave in a
similar way - it's mostly just an apt frontend here.
?