Re:Re: IceCat-78.2 preview on 'wip-icecat-78' branch; need icedove-78.

[Zhu Zihao]

Patches sent to http://debbugs.gnu.org/cgi/bugreport.cgi?bug=43663


Please review, thanks!








At 2020-09-28 04:15:42, "Mark H Weaver"  wrote:
>Hi,
>
>"Zhu Zihao"  writes:
>
>> @@ -1017,10 +1010,31 @@ from forcing GEXP-PROMISE."
>> (lambda _
>>   (use-modules (guix build cargo-utils))
>>   (let ((null-hash 
>> "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"))
>> -   (substitute* '("Cargo.lock" "gfx/wr/Cargo.lock")
>> - (("(\"checksum .* = )\".*\"" all name)
>> -  (string-append name "\"" null-hash "\"")))
>> -   (generate-all-checksums "third_party/rust"))
>> +   (for-each (lambda (file)
>> +   (format #t "patching checksums in ~a~%" file)
>> +   (substitute* (find-files "." "Cargo.lock$")
>> + (("^checksum = \".*\"")
>> +  (string-append "checksum = \"" null-hash 
>> "\""
>> + (find-files "." "Cargo.lock$"))
>[...]
>> Why we need another `find-files` in `substitute*`? The outer
>> `find-files` should find all locks file for you, maybe you can use the
>> arg of lambda instead.
>
>Indeed, that's clearly what I had intended to do, but then I apparently
>forgot a step.  Good catch, thanks!
>
>> @@ -756,8 +750,8 @@ from forcing GEXP-PROMISE."
>> ("libxt" ,libxt)
>> ("libffi" ,libffi)
>> ("ffmpeg" ,ffmpeg)
>> -   ("libvpx" ,libvpx)
>> -   ("icu4c" ,icu4c)
>> +   ;; UNBUNDLE-ME! ("libvpx" ,libvpx)
>> +   ;; UNBUNDLE-ME! ("icu4c" ,icu4c)
>> ("pixman" ,pixman)
>> ("pulseaudio" ,pulseaudio)
>> ("mesa" ,mesa)
>>
>> IceCat 78 may need icu4c v67, which variable name is `icu4c-67` in
>> guix channel.
>
>Good idea!  Would you like to propose a patch, test it, and report back?
>If not, I'll try it eventually.  I would certainly be very glad to
>reduce the number of bundled libraries in our IceCat package, which
>seems to be getting worse over time.  Any help on that effort would be
>much appreciated.
>
>   Best,
>Mark

Re: IceCat-78.2 preview on 'wip-icecat-78' branch; need icedove-78.

[Mark H Weaver]

Jonathan Brielmaier  writes:
> I updated the patches in the mean time for 78.3.0, see
> http://issues.guix.gnu.org/43647

Thank you, Jonathan!  Your updated patches look good to me.
I've followed up at  and we can
continue the discussion there.

 Best,
  Mark

Re: emacs-lucid (was Re: Emacs closure at ~900MB?)

[Bonface M. K.]

Pierre Neidhardt  writes:

> Just tested, EXWM works with emacs-no-x-toolkit!
>

Just tested it too, and it works for me too :)

> So I suggest we add the following packages:
>
> (define-public emacs-no-x-toolkit-xelb
>(package
>  (inherit emacs-xelb)
>  (name "emacs-no-x-toolkit-xelb")
>  (arguments
>   (substitute-keyword-arguments (package-arguments emacs-xelb)
> ((#:emacs emacs) `,emacs-no-x-toolkit)
>
> (define-public emacs-no-x-toolkit-exwm 
>(package
>  (inherit emacs-exwm)
>  (name "emacs-no-x-toolkit-exwm")
>  (synopsis "Emacs X window manager (without X toolkit)")
>  (propagated-inputs
>   `(("emacs-no-x-toolkit-xelb" ,emacs-no-x-toolkit-xelb)))
>  (arguments
>   (substitute-keyword-arguments (package-arguments emacs-exwm)
> ((#:emacs emacs) `,emacs-no-x-toolkit)
>
> Thoughts?

Wouldn't that be redundant? If you wanted to use
EXWM, we already have EXWM provided on MELPA, so
you could just set that up. That's IMHO though.

-- 
Bonface M. K. (https://www.bonfacemunyoki.com)
Chief Emacs Mchochezi / Twitter: @BonfaceKilz
GPG key = D4F09EB110177E03C28E2FE1F5BBAE1E0392253F


signature.asc
Description: PGP signature

Re: IceCat-78.2 preview on 'wip-icecat-78' branch; need icedove-78.

[Mark H Weaver]

Hi,

"Zhu Zihao"  writes:

> @@ -1017,10 +1010,31 @@ from forcing GEXP-PROMISE."
> (lambda _
>   (use-modules (guix build cargo-utils))
>   (let ((null-hash 
> "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"))
> -   (substitute* '("Cargo.lock" "gfx/wr/Cargo.lock")
> - (("(\"checksum .* = )\".*\"" all name)
> -  (string-append name "\"" null-hash "\"")))
> -   (generate-all-checksums "third_party/rust"))
> +   (for-each (lambda (file)
> +   (format #t "patching checksums in ~a~%" file)
> +   (substitute* (find-files "." "Cargo.lock$")
> + (("^checksum = \".*\"")
> +  (string-append "checksum = \"" null-hash 
> "\""
> + (find-files "." "Cargo.lock$"))
[...]
> Why we need another `find-files` in `substitute*`? The outer
> `find-files` should find all locks file for you, maybe you can use the
> arg of lambda instead.

Indeed, that's clearly what I had intended to do, but then I apparently
forgot a step.  Good catch, thanks!

> @@ -756,8 +750,8 @@ from forcing GEXP-PROMISE."
> ("libxt" ,libxt)
> ("libffi" ,libffi)
> ("ffmpeg" ,ffmpeg)
> -   ("libvpx" ,libvpx)
> -   ("icu4c" ,icu4c)
> +   ;; UNBUNDLE-ME! ("libvpx" ,libvpx)
> +   ;; UNBUNDLE-ME! ("icu4c" ,icu4c)
> ("pixman" ,pixman)
> ("pulseaudio" ,pulseaudio)
> ("mesa" ,mesa)
>
> IceCat 78 may need icu4c v67, which variable name is `icu4c-67` in
> guix channel.

Good idea!  Would you like to propose a patch, test it, and report back?
If not, I'll try it eventually.  I would certainly be very glad to
reduce the number of bundled libraries in our IceCat package, which
seems to be getting worse over time.  Any help on that effort would be
much appreciated.

   Best,
Mark

Re: Contribute to the translation of the user manual

[Julien Lepiller]

Le 27 septembre 2020 16:03:28 GMT-04:00, Hubert Lombard 
 a écrit :
>
>Hi Guix !

Hi Hubert!

>
>As a very basic end user of the Free Software, for more than 2 years, I
>have been using Guix System with pleasure. Also, it really helps me.
>
>I would like to help with the translation.
>
>The manual is translated my native language (french), however I noticed
>that some passages are left in English.

I'm the main translator for the French language, and I'm glad you're willing to 
help!

>
>eg:
>https://guix.gnu.org/manual/fr/html_node/Installer-Guix-dans-une-VM.html
>(isolated phrases in parts 3 and 4).
>
>I also found other concerned sentences in a few pages.
>
>Could I try to help with this? 
>
>Having never participated in the life of a free software, it would be a
>great pleasure for me to be able to contribute to Guix as a translator
>of the manual... and maybe later for other things... Complete noob in
>the matter, I have never used .po files, but I guess it's not difficult
>:-)
>
>The FSF has confirmed receipt of the document, all I'll have to do is
>send an email to the coordinator to indicate which documents I would
>like to translate. (From https://traduc.org/Projet_de_traduction/)

There's no need to give your copyright to the FSF to contribute to the 
translation of Guix. Individual contributors keep their copyright.

There is an issue with the current po files though, as they don't list the 
correct license. They are currently under "the same license as the guix 
package" (gpl3+), but it should be "the same license as the guix manual" 
(gfdl). As long as you agree to this change, I can let you contribute :)

I see that I'm not specifically assigned to the cranslation of the manual, so 
as long as you accept the above-mentionned change you can simply use the robot 
at the TP.

Note that we are planning to move to a weblate instance soonish, but we're 
still using the TP for now.

>
>The last/current step about the mailing list: "Confirmed requests for
>Traduc and Traduc-po subscriptions."
>
>Thanks in advance for your answer
>
>Good continuation, this project is becoming a practical reality and the
>childhurds seem great.
>
>Kind regards
>
>Hubert

Contribute to the translation of the user manual

[Hubert Lombard]

Hi Guix !

As a very basic end user of the Free Software, for more than 2 years, I have 
been using Guix System with pleasure. Also, it really helps me.

I would like to help with the translation.

The manual is translated my native language (french), however I noticed that 
some passages are left in English.

eg: https://guix.gnu.org/manual/fr/html_node/Installer-Guix-dans-une-VM.html 
(isolated phrases in parts 3 and 4).

I also found other concerned sentences in a few pages.

Could I try to help with this? 

Having never participated in the life of a free software, it would be a great 
pleasure for me to be able to contribute to Guix as a translator of the 
manual... and maybe later for other things... Complete noob in the matter, I 
have never used .po files, but I guess it's not difficult :-)

The FSF has confirmed receipt of the document, all I'll have to do is send an 
email to the coordinator to indicate which documents I would like to translate. 
(From https://traduc.org/Projet_de_traduction/)

The last/current step about the mailing list: "Confirmed requests for Traduc 
and Traduc-po subscriptions."

Thanks in advance for your answer

Good continuation, this project is becoming a practical reality and the 
childhurds seem great.

Kind regards

Hubert
-- 

Re: IceCat-78.2 preview on 'wip-icecat-78' branch; need icedove-78.

[Jonathan Brielmaier]

On 22.09.20 21:00, Jonathan Brielmaier wrote:

On 15.09.20 12:52, Mark H Weaver wrote:

Hi Jonathan,

Jonathan Brielmaier  writes:

I had a look. It's at the moment two WIP patches here:
https://gitlab.com/jonsger/Guix/-/tree/wip-icedove-78


Thanks very much for working on it.


Icedove 78 needs nss >= 3.53.1 and we have only 3.52.1.


An easy solution for now would be to use the bundled NSS, by simply
removing --with-system-nss from the mozconfig and removing 'nss' from
the inputs.  What do you think?


In the mean time I got icedove 78 working. The two patches are attached.

gnu: Add nss@3.56.
- It's basically like nss 3.52.1 apart from two files are gone in
'install phase. The only way I found is to copy all phases over and
remove those two lines.
```
(delete-file (string-append lib "/libgtest1.so"))
(delete-file (string-append lib "/libgtestutil.so"))
```
- nss-3.56-pkgconfig.patch is like nss-pkgconfig.patch with only
difference in a slightly adjusted nss/manifest.mn diff. I don't know how
to do that more elegant

gnu: icedove: Update to 78.2.2.
- Mostly house keeping and some updates of components. To get icedove
run properly we need icedove-78-fix-new-page.patch, otherwise it's
completely broken. I found no other way to add it, then to use the
release tarball instead of the icecat sources.

~Jonathan
Sent from Icedove 78 :P


I updated the patches in the mean time for 78.3.0, see
http://issues.guix.gnu.org/43647

Re: IceCat-78.2 preview on 'wip-icecat-78' branch; need icedove-78.

[Zhu Zihao]

@@ -1017,10 +1010,31 @@ from forcing GEXP-PROMISE."
(lambda _
  (use-modules (guix build cargo-utils))
  (let ((null-hash 
"e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"))
-   (substitute* '("Cargo.lock" "gfx/wr/Cargo.lock")
- (("(\"checksum .* = )\".*\"" all name)
-  (string-append name "\"" null-hash "\"")))
-   (generate-all-checksums "third_party/rust"))
+   (for-each (lambda (file)
+   (format #t "patching checksums in ~a~%" file)
+   (substitute* (find-files "." "Cargo.lock$")
+ (("^checksum = \".*\"")
+  (string-append "checksum = \"" null-hash "\""
+ (find-files "." "Cargo.lock$"))
+   (for-each generate-all-checksums
+ '("services"
+   "js"
+   "third_party/rust"
+   "dom/media"
+   "dom/webauthn"
+   "toolkit"
+   "gfx"
+   "storage"
+   "modules"
+   "xpcom/rust"
+   "media"
+   "mozglue/static/rust"
+   "netwerk"
+   "remote"
+   "intl"
+   "servo"
+   "security/manager/ssl"
+   "build")))




Why we need another `find-files` in `substitute*`? The outer `find-files` 
should find all locks file for you, maybe you can use the arg of lambda instead.


@@ -756,8 +750,8 @@ from forcing GEXP-PROMISE."
("libxt" ,libxt)
("libffi" ,libffi)
("ffmpeg" ,ffmpeg)
-   ("libvpx" ,libvpx)
-   ("icu4c" ,icu4c)
+   ;; UNBUNDLE-ME! ("libvpx" ,libvpx)
+   ;; UNBUNDLE-ME! ("icu4c" ,icu4c)
("pixman" ,pixman)
("pulseaudio" ,pulseaudio)
("mesa" ,mesa)



IceCat 78 may need icu4c v67, which variable name is `icu4c-67` in guix channel.

Mailing Lists List

[Greg Hogan]

When I google for “guix mailing lists” I am directed to
  https://savannah.gnu.org/mail/?group=guix 

which does not include guix-devel. It is returned as my second google link and 
also of course listed on the Guix website but would be helpful to include on 
Savannah.

Greg

Building a library as both static and dynamic

[Greg Hogan]

Is there a best practice or example for building a library twice, both static 
and dynamic? I submitted patch #43620, and in working on another library have 
the same issue. These are cmake builds with a parameter declaration for either 
a static or dynamic build, not both. I would like to create a single package 
with both “out” and “static” outputs, which looks to be standard across Guix.

One idea is to run the configure / make / make install phases twice. 
modify-phases does not currently support copying phases (though add-after could 
work with the right function reference from cmake-build) and #:configure-flags 
would need to be set differently.

Another option would be to patch the source build files, but this problem feels 
solvable in Guix without duplicating the code from cmake-build’s configure.

Thanks,
Greg

Re: emacs-lucid (was Re: Emacs closure at ~900MB?)

[Pierre Neidhardt]

I'll test EXWM with emacs-no-x-toolkit.

I think the discussion around emacs-lucid started out of ignorance for
the emacs-no-x-toolkit package.  If the latter happens to be a better
option, I propose that we don't add emacs-lucid but instead advertise
emacs-no-x-toolkit better, say, mention it in the description of the
"emacs" package.

-- 
Pierre Neidhardt
https://ambrevar.xyz/


signature.asc
Description: PGP signature