From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnaud B Subject: Unison GTK UI in unison package Date: Mon, 2 Apr 2018 14:10:22 +0200 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="f4f5e80c6c547647330568dc7906" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53026) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f2yI6-0005qZ-EM for help-guix@gnu.org; Mon, 02 Apr 2018 08:10:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f2yI5-0002Q3-BS for help-guix@gnu.org; Mon, 02 Apr 2018 08:10:26 -0400 Received: from mail-wm0-x22b.google.com ([2a00:1450:400c:c09::22b]:55055) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f2yI4-0002Oy-Qe for help-guix@gnu.org; Mon, 02 Apr 2018 08:10:24 -0400 Received: by mail-wm0-x22b.google.com with SMTP id h76so25035450wme.4 for ; Mon, 02 Apr 2018 05:10:24 -0700 (PDT) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: help-guix@gnu.org --f4f5e80c6c547647330568dc7906 Content-Type: text/plain; charset="UTF-8" Hello all, I looked at the ocaml.scm file where the unison package is defined, together with ocaml, lablgtk and a number of other related tools. It uses the gtk module (gnu packages gtk), in which there is pango as well. So it seems everything is in place to build unison and at the same time its graphical version, according to the build instructions given for that. But in the end in my GuixSD as the user having done the installation, I just end up with the CLI unison and not unison-gtk2 as expected. I tried explicitly installing various packages such as gtk+, lablgtk, and then rebuilding the unison package, to no avail. Many thanks in advance if someone can help. Arnaud --f4f5e80c6c547647330568dc7906 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hel= lo all,
I looked at the ocaml.scm file where the unison package is defined, togeth= er with ocaml, lablgtk and a number of other related tools. It uses the gtk= module (gnu packages gtk), in which there is pango as well.
So it seems everything is= in place to build unison and at the same time its graphical version, accor= ding to the build instructions given for that.
But in the end in my GuixS= D as the user having done the installation, I just end up with the CLI unis= on and not unison-gtk2 as expected.
I tried explicitly installing various packages suc= h as gtk+, lablgtk, and then rebuilding the unison package, to no avail.

Many than= ks in advance if someone can help.
Arnaud

--f4f5e80c6c547647330568dc7906-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: Unison GTK UI in unison package Date: Mon, 2 Apr 2018 16:16:05 -0400 Message-ID: <20180402201605.GA3852@jasmine.lan> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="SUOF0GtieIMvvwua" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47694) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f35sC-0000i7-N8 for help-guix@gnu.org; Mon, 02 Apr 2018 16:16:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f35s8-00009c-3O for help-guix@gnu.org; Mon, 02 Apr 2018 16:16:12 -0400 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:37401) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1f35s7-00008w-Sc for help-guix@gnu.org; Mon, 02 Apr 2018 16:16:08 -0400 Content-Disposition: inline In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Arnaud B Cc: help-guix@gnu.org --SUOF0GtieIMvvwua Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Apr 02, 2018 at 02:10:22PM +0200, Arnaud B wrote: > I looked at the ocaml.scm file where the unison package is defined, > together with ocaml, lablgtk and a number of other related tools. It uses > the gtk module (gnu packages gtk), in which there is pango as well. > So it seems everything is in place to build unison and at the same time its > graphical version, according to the build instructions > > given for that. > But in the end in my GuixSD as the user having done the installation, I > just end up with the CLI unison and not unison-gtk2 as expected. > I tried explicitly installing various packages such as gtk+, lablgtk, and > then rebuilding the unison package, to no avail. Basically, the packages that are required to build the Unison GUI, such as lablgtk, GTK+ itself, etc, are not present in the environment where Unison is built by Guix. They may be defined in the same source file as the Unison package, or they may be imported by that file, but this does not mean they are present in the Unison build environment. Additionally, installing a package with `guix package --install` has no effect on how packages are built. Each time Guix builds a package, it uses an isolated environment that only includes the software specified in the package definition of the package being built, as well as "implicit" dependencies that come with the specified build system. To make progress on building the Unison GUI, I recommend adding the required packages to a new inputs field in the Unison package definition. You can copy the structure of the native-inputs field for this. I recommend reading the Introduction of the Guix manual [0], and continuing to other sections as your interest allows. You will also find some useful info in Package Reference [1]. Please don't hesitate to ask more questions here or on the Guix IRC channel, #guix on Freenode. [0] https://www.gnu.org/software/guix/manual/html_node/Introduction.html [1] https://www.gnu.org/software/guix/manual/html_node/package-Reference.html --SUOF0GtieIMvvwua Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlrCj4AACgkQJkb6MLrK fwhlZRAA0KH34SfuC/Qrag1l5m/HXPFjsjPos1GoYTXeMls/hWG6uQx0d7XzF8Jv oBapmt/b5+GrjLZDv701B3o4oy9vxP+n/UquxtB9riLjpc6jQK12NT6/bUS4SQZS hfPJBPawxdpA4GIKPivV+WrU+XSaOr7EhQgf3o7z19R6dk4q0KcrZqX6xxxIhd+X SFh6FRRqXKTUU5/9TsnAAQtDSpU5oZ3LEXN9T75GYClektNHjGo6GaQegcAdg9uJ 2CyAYRLlBsqaUwIRyjc1fdFOm1SnX/Jg8mOU2boQ6/ct8dr0OYAoLWBUbchHA3Ek gfcch5DO7vTD91eiyoF7SkZ5yU6eWtI+NciW44+tKnFDTrKak/aJI+YxIGhpFgv0 uqkUS3ZSv0XTIGQP3Ih1wmIzJ8FdVgJfykXlbRWetzlAAOJEF3JaIHTgkfXwxwHk 2gsGL/uTsPiCWQMRI/HpezomaFLMVl3L0TjQDyN2M6leSdYfm2KV9Jz7DdVjpvqG MwiDluny1QdmMs8cRIS7zsn3AT9Hbwv2/mdLLUtHiX/95M07fWqZUUX/il7hS5kf OxLFpsoHg5nPqAVK7KYVbRQlEWSI4+J+2kCPeLJqQUJtgdZIlVq9L8c6XS9K24dp 8xQrULi37opAEm4HHy1g25+wvFkehvf+pgXmmeM/iH+tXwbdzsE= =8ZIB -----END PGP SIGNATURE----- --SUOF0GtieIMvvwua-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnaud B Subject: Re: Unison GTK UI in unison package Date: Tue, 3 Apr 2018 23:24:33 +0200 Message-ID: References: <20180402201605.GA3852@jasmine.lan> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="089e08241f303b47b80568f85544" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38512) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f3TQ0-0005Pm-Fe for help-guix@gnu.org; Tue, 03 Apr 2018 17:24:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f3TPy-0006TW-QS for help-guix@gnu.org; Tue, 03 Apr 2018 17:24:40 -0400 Received: from mail-lf0-x234.google.com ([2a00:1450:4010:c07::234]:33766) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f3TPy-0006TB-DJ for help-guix@gnu.org; Tue, 03 Apr 2018 17:24:38 -0400 Received: by mail-lf0-x234.google.com with SMTP id x70-v6so15459627lfa.0 for ; Tue, 03 Apr 2018 14:24:38 -0700 (PDT) In-Reply-To: <20180402201605.GA3852@jasmine.lan> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Leo Famulari , help-guix@gnu.org --089e08241f303b47b80568f85544 Content-Type: text/plain; charset="UTF-8" Hello Leo As you may have seen I'm trying to complete the process of packaging FreeFileSync. As soon as this is hopefully done - or decidedly way above my current ability -, I'll come back to the Unison case, thanks to your enlightnening input. Thanks for that Arnaud 2018-04-02 22:16 GMT+02:00 Leo Famulari : > On Mon, Apr 02, 2018 at 02:10:22PM +0200, Arnaud B wrote: > > I looked at the ocaml.scm file where the unison package is defined, > > together with ocaml, lablgtk and a number of other related tools. It uses > > the gtk module (gnu packages gtk), in which there is pango as well. > > > So it seems everything is in place to build unison and at the same time > its > > graphical version, according to the build instructions > > > > > given for that. > > But in the end in my GuixSD as the user having done the installation, I > > just end up with the CLI unison and not unison-gtk2 as expected. > > I tried explicitly installing various packages such as gtk+, lablgtk, and > > then rebuilding the unison package, to no avail. > > Basically, the packages that are required to build the Unison GUI, such > as lablgtk, GTK+ itself, etc, are not present in the environment where > Unison is built by Guix. They may be defined in the same source file as > the Unison package, or they may be imported by that file, but this does > not mean they are present in the Unison build environment. Additionally, > installing a package with `guix package --install` has no effect on how > packages are built. > > Each time Guix builds a package, it uses an isolated environment that > only includes the software specified in the package definition of the > package being built, as well as "implicit" dependencies that come with > the specified build system. > > To make progress on building the Unison GUI, I recommend adding the > required packages to a new inputs field in the Unison package > definition. You can copy the structure of the native-inputs field for > this. > > I recommend reading the Introduction of the Guix manual [0], and > continuing to other sections as your interest allows. You will also find > some useful info in Package Reference [1]. > > Please don't hesitate to ask more questions here or on the Guix IRC > channel, #guix on Freenode. > > [0] > https://www.gnu.org/software/guix/manual/html_node/Introduction.html > > [1] > https://www.gnu.org/software/guix/manual/html_node/package-Reference.html > --089e08241f303b47b80568f85544 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hel= lo Leo
As y= ou may have seen I'm trying to complete the process of packaging FreeFi= leSync.
As= soon as this is hopefully done - or decidedly way above my current ability= -, I'll come back to the Unison case, thanks to your enlightnening inp= ut. Thanks for that
Arnaud

2018-04-02 22:16 GMT+02:00 Leo Famulari <= ;leo@famulari.name>:
On Mon, A= pr 02, 2018 at 02:10:22PM +0200, Arnaud B wrote:
> I looked at the ocaml.scm file where the unison package is defined, > together with ocaml, lablgtk and a number of other related tools. It u= ses
> the gtk module (gnu packages gtk), in which there is pango as well.
> So it seems everything is in place to build unison and at the same tim= e its
> graphical version, according to the build instructions
> <https://webda= v.seas.upenn.edu/svn/unison/branches/2.48/src/INSTALL.gtk2>= ;
> given for that.
> But in the end in my GuixSD as the user having done the installation, = I
> just end up with the CLI unison and not unison-gtk2 as expected.
> I tried explicitly installing various packages such as gtk+, lablgtk, = and
> then rebuilding the unison package, to no avail.

Basically, the packages that are required to build the Unison GUI, s= uch
as lablgtk, GTK+ itself, etc, are not present in the environment where
Unison is built by Guix. They may be defined in the same source file as
the Unison package, or they may be imported by that file, but this does
not mean they are present in the Unison build environment. Additionally, installing a package with `guix package --install` has no effect on how
packages are built.

Each time Guix builds a package, it uses an isolated environment that
only includes the software specified in the package definition of the
package being built, as well as "implicit" dependencies that come= with
the specified build system.

To make progress on building the Unison GUI, I recommend adding the
required packages to a new inputs field in the Unison package
definition. You can copy the structure of the native-inputs field for
this.

I recommend reading the Introduction of the Guix manual [0], and
continuing to other sections as your interest allows. You will also find some useful info in Package Reference [1].

Please don't hesitate to ask more questions here or on the Guix IRC
channel, #guix on Freenode.

[0]
https://www.gnu.org/software/guix/manual/html_node/Introduction.html

[1]
https://www.gnu.org/softwar= e/guix/manual/html_node/package-Reference.html

--089e08241f303b47b80568f85544-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marco van Hulten Subject: Re: Unison GTK UI in unison package Date: Wed, 25 Mar 2020 10:18:19 +0100 Message-ID: <20200325101819.59e53a0f@jasniac.instanton> References: <20180402201605.GA3852@jasmine.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/_10LGlARohMve4CF_NGVVgq"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:52151) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jH2Be-000170-FS for help-guix@gnu.org; Wed, 25 Mar 2020 05:19:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jH2Bd-00047X-4l for help-guix@gnu.org; Wed, 25 Mar 2020 05:18:58 -0400 Received: from alfons.uib.no ([2001:700:200:30::141]:41586) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1jH2Bc-00041h-Hy for help-guix@gnu.org; Wed, 25 Mar 2020 05:18:57 -0400 In-Reply-To: <20180402201605.GA3852@jasmine.lan> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane-mx.org@gnu.org Sender: "Help-Guix" To: help-guix@gnu.org Cc: Arnaud B --Sig_/_10LGlARohMve4CF_NGVVgq Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello=E2=80=94 To synchronise file with a server I don't operate, I would like to use unison@2.48.15 on my Guix System, preferably the GUI*. The last e-mail I could find about this on the mailinglists looks relevant. Je 2 apr 2018 16:16 skribis Leo: > On Mon, Apr 02, 2018 at 02:10:22PM +0200, Arnaud B wrote: > > I looked at the ocaml.scm file where the unison package is defined, > > together with ocaml, lablgtk and a number of other related tools. It us= es > > the gtk module (gnu packages gtk), in which there is pango as well. =20 >=20 > > So it seems everything is in place to build unison and at the same time= its > > graphical version, according to the build instructions > > > > given for that. > > But in the end in my GuixSD as the user having done the installation, I > > just end up with the CLI unison and not unison-gtk2 as expected. > > I tried explicitly installing various packages such as gtk+, lablgtk, a= nd > > then rebuilding the unison package, to no avail. =20 >=20 > Basically, the packages that are required to build the Unison GUI, such > as lablgtk, GTK+ itself, etc, are not present in the environment where > Unison is built by Guix. They may be defined in the same source file as > the Unison package, or they may be imported by that file, but this does > not mean they are present in the Unison build environment. Additionally, > installing a package with `guix package --install` has no effect on how > packages are built. >=20 > Each time Guix builds a package, it uses an isolated environment that > only includes the software specified in the package definition of the > package being built, as well as "implicit" dependencies that come with > the specified build system. >=20 > To make progress on building the Unison GUI, I recommend adding the > required packages to a new inputs field in the Unison package > definition. You can copy the structure of the native-inputs field for > this. >=20 > I recommend reading the Introduction of the Guix manual [0], and > continuing to other sections as your interest allows. You will also find > some useful info in Package Reference [1]. >=20 > Please don't hesitate to ask more questions here or on the Guix IRC > channel, #guix on Freenode. >=20 > [0] > https://www.gnu.org/software/guix/manual/html_node/Introduction.html >=20 > [1] > https://www.gnu.org/software/guix/manual/html_node/package-Reference.html Arnaud, did you ever look into this again? Did you find a solution for synchronising between Guix and the other system? I vaguely remember that at some time there were several Unison versions available on Guix. Of course, I might try to build Unison 2.51.2 on the non-Guix system. =E2=80=94Marco * Works nice to put unison-gtk in .xinitrc, before and after running your window manager. --Sig_/_10LGlARohMve4CF_NGVVgq Content-Type: application/pgp-signature Content-Description: OpenPGP digitale handtekening -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEDZPVdgAMKNh/RNOWn8NzTfuEQA0FAl57Id0ACgkQn8NzTfuE QA2aQg//WHMBM4yE6Tyk+XGkjO7BbEvIlUVOEXS3BUqcRasF/5UYjO8VHtSbc01f g552VZFnvEGPO6tIIaENgB5lEBlcekyVOzCyQbUDnea0e4u69Q2NCPubjGkNyWyx saeX4wtL3njQRM1SOT3/v4UkqehW3Cb8px9/cRl0iCnBIPaGKSu4IQmqL035ZXPn AX0ibKUPUvT+LXLJ0L0UrhNCgMgPgPGAcvll4pyiv4e7ufkiIcKsanBaERbBEYGT ohbW7XtFXX64d4lasFPz7X0M1is4ZVw56S669gJQbBu3+iou6QVMmCJppLYTwcig G9yMQ1UAJyuc7b0Tu6a+C8+o4To4orm78M0tgMWRqGzC+GcEmSBuGNuSKS1kOgOZ uwLSmQGtaSFZ2qGF9oPs0Jvzcb176OD2wD/AKvcNMNhHuhsbPXq8/XL14rXG3o/H ssattA4ydBYZ5UeO+W2GeKGZ1+0DrhAOscpr2FzQp+WC4wNvTiUdW7UV/xqa0Pjh VmLt170vfOmlUcMj6GfVmY0BGa/EGnOSvb7fmROFWQQ0UOCGfGj6VF+yHy9ry20S VsLRmvU40/LxbpwMXbKkBtaS9M8HWVCQ1SBSXCxfdluFgB6vK+ReYDEnQplmluoL 9DAQ8dpnMhYyZA1wdDaMk7JuPX8mC9ys/UHu9RsJ8WXg56sH6Go= =GUs2 -----END PGP SIGNATURE----- --Sig_/_10LGlARohMve4CF_NGVVgq--