[Top][All Lists]

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

[bug#41818] [PATCH] gnu: Add syncthing-gtk.

From: paul
Subject: [bug#41818] [PATCH] gnu: Add syncthing-gtk.
Date: Tue, 30 Jun 2020 17:43:11 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Icedove/68.9.0

Hi Marius,

On 6/22/20 10:16 PM, Marius Bakke wrote:
Giacomo Leidi <> writes:

* gnu/packages/syncthing.scm (syncthing-gtk): New variable.
+    (build-system python-build-system)
+    (arguments
+     `(#:python ,python-2))
+    (propagated-inputs
+     `(("python2-bcrypt" ,python2-bcrypt)
+       ("python2-dateutil" ,python2-dateutil)
+       ("python2-pycairo" ,python2-pycairo)
+       ("python2-pygobject" ,python2-pygobject)
+       ("python-nautilus" ,python-nautilus)
+       ("libappindicator" ,libappindicator)
+       ("libnotify" ,libnotify)
+       ("psmisc" ,psmisc)
+       ("syncthing" ,syncthing)))
I don't think these needs to be propagated, as the 'syncthing-gtk'
executable will be automatically wrapped with a PYTHONPATH that contains
the Python inputs.
I didn't know that, I really should study deeper the build systems.
I'm not sure about libappindicator, libnotify and psmisc though.
Ideally we'd insert absolute references where appropriate to avoid
propagation.  In the worst case we can wrap it with those in PATH.

Can you look into it and send an updated patch?

As you suggested I managed to move all propagated-inputs to the inputs field, I'm not sure I did it right but from my tests the package seem to be working.

I'm attaching an updated version of the patch, I apologize for the delay.


Attachment: 0001-gnu-Add-syncthing-gtk.patch
Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]