unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Brendan Tildesley <mail@brendan.scot>, 47870@debbugs.gnu.org
Subject: [bug#47870] [PATCH 1/2] gnu: polkit-gnome: Add autostart .desktop file.
Date: Mon, 19 Apr 2021 14:01:02 +0200	[thread overview]
Message-ID: <10ddc05d03469890073e218715a1a6c74151e2a9.camel@student.tugraz.at> (raw)
In-Reply-To: <752594641.90411.1618831613893@office.mailbox.org>

Am Montag, den 19.04.2021, 13:26 +0200 schrieb Brendan Tildesley:
> > On 04/19/2021 1:12 PM Leo Prikler <leo.prikler@student.tugraz.at>
> > wrote:
> > 
> >  
> > Hi Brendan,
> > 
> > That's a pretty large package description for something rather
> > trivial.
> > Would the following work instead?
> > 
> >   (package/inherit mate-polkit
> >     (arguments
> >      `(#:phases
> >        (modify-phases %standard-phases
> >          (add-after 'unpack 'patch-desktop-for-xfce
> >            (lambda _
> >              (substitute* "src/polkit-mate-authentication-agent-
> > 1.desktop.in.in"
> >                  (("MATE;") "XFCE;"))))))))
> > 
> > Regards,
> > Leo
> Uhh ok it's simpler source code but now we're building it twice,
> potentially having two copies of it and the .desktop file will have
> the same filename and thus conflict if both desktops are installed.
Oh, right, I was missing the part, in which we rename it.
W.r.t. "building it twice", that's only if you have both mate-polkit
and the new one in your profile, in which case I guess it would be
tolerable.  If you're using just MATE or just XFCE you'll build one or
the other.

FWIW, there is also xfce-polkit [1], but it was last updated 2020 with
the latest release in 2018 (which is still more recent than 2011,
though).  WDYT?

[1] https://github.com/ncopa/xfce-polkit





  reply	other threads:[~2021-04-19 12:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-18 13:13 [bug#47870] [PATCH 0/2] Autostart polkit-gnome in XFCE Brendan Tildesley via Guix-patches via
2021-04-18 13:17 ` [bug#47870] [PATCH 1/2] gnu: polkit-gnome: Add autostart .desktop file Brendan Tildesley
2021-04-18 13:17   ` [bug#47870] [PATCH 2/2] gnu: xfce: Start polkit-gnome agent on login Brendan Tildesley
2021-04-18 14:47   ` [bug#47870] [PATCH 1/2] gnu: polkit-gnome: Add autostart .desktop file Leo Prikler
2021-04-18 15:15     ` Brendan Tildesley
2021-04-18 15:52       ` Leo Prikler
2021-04-19  6:56         ` Brendan Tildesley
2021-04-19  7:36           ` Leo Prikler
2021-04-19 11:02             ` Brendan Tildesley
2021-04-19 11:12               ` Leo Prikler
2021-04-19 11:26                 ` Brendan Tildesley
2021-04-19 12:01                   ` Leo Prikler [this message]
2021-04-19 13:30                     ` Brendan Tildesley
2021-04-19 13:47                       ` Leo Prikler
2021-04-21  5:31                         ` Brendan Tildesley
2021-04-21  8:44                           ` bug#47870: " Leo Prikler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=10ddc05d03469890073e218715a1a6c74151e2a9.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=47870@debbugs.gnu.org \
    --cc=mail@brendan.scot \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).