Re: 29/88: gnu: Add emacs-let-alist.

[Oleg Pykhalov]

In addion to my previous answer.

Oleg Pykhalov  writes:

[…]

>> 'let-alist' is a part of Emacs (that's why it was removed by commit
>> 469c7ce0¹).  Is there a reason to add it?

[…]

> Elpa importer could probably exclude ‘let-alist’ in ‘propagated-inputs’.

Should I remove ‘let-alist’ now?  Maybe we could implement exclude
mechanism for ‘let-alist’ and then remove ‘let-alist’?  ‘let-alist’
shouln't clutter much if it stays in Guix package collection for a time.

Oleg.


signature.asc
Description: PGP signature

Re: Packaging a free Firefox

[Mike Gerwitz]

On Fri, May 04, 2018 at 16:24:11 +0200, Pjotr Prins wrote:
> On Thu, May 03, 2018 at 01:59:24PM -0400, Mike Gerwitz wrote:
>> I use IceCat personally and FF Dev Edition at work.  Until the recent
>> move to WebExtensions, I used the same addons.  I use NoScript and Tor
>> and have no problems.  But I rarely enable JS and never run proprietary
>> JS, so my exposure may be different.  I do not use LibreJS (because I
>> don't usually run JS at all in general and it historically did not play
>> well with NoScript; maybe that has changed).
>
> Disabling all extensions makes Icecat work much better. I'll try it as
> a default now.

I don't think I made clear with the above: I use many different addons
(NoScript, Privacy Badger, HTTPS Everywhere, uBlock Origin,
Self-Destructing Cookies, Foxyproxy, Tree Style Tab, and some misc
ones); I didn't want to give the impression that extensions are a
problem for me.

As far as the extensions that come _with_ IceCat, I just don't have use
for them or use something else in place of them.

-- 
Mike Gerwitz
Free Software Hacker+Activist | GNU Maintainer & Volunteer
GPG: D6E9 B930 028A 6C38 F43B  2388 FEF6 3574 5E6F 6D05
https://mikegerwitz.com


signature.asc
Description: PGP signature

Re: Packaging a free Firefox

[Nils Gillmann]

Pjotr Prins transcribed 650 bytes:
> On Thu, May 03, 2018 at 01:59:24PM -0400, Mike Gerwitz wrote:
> > I use IceCat personally and FF Dev Edition at work.  Until the recent
> > move to WebExtensions, I used the same addons.  I use NoScript and Tor
> > and have no problems.  But I rarely enable JS and never run proprietary
> > JS, so my exposure may be different.  I do not use LibreJS (because I
> > don't usually run JS at all in general and it historically did not play
> > well with NoScript; maybe that has changed).
> 
> Disabling all extensions makes Icecat work much better. I'll try it as
> a default now.
> 
> Question: why do we switch on extensions by default? Sure confused my
> experience.
>
> Pj.

I think it's because this is upstreams decision and we usually stick
with what upstream does. Although you could almost call our Icecat
a variant of Icecat due to more work going into tracking Mozilla
and applying patches done by Mark.

Re: Introducing myself as an Outreachy Intern

[Christopher Lemmer Webber]

Ricardo Wurmus writes:

> Welcome Sahithi!
>
>> I Sahithi Yarlagadda, a Free Software enthusiast. I am from India,
>> pursuing my under graduation final semester in Computer Science. I will
>> be working as an Outreachy Intern for May-August 2018. I am glad to be
>> part of Guix Community. I have been working with Ricardo Wurmus during
>> the application process. He helped me in understanding and working with
>> Guix. Community has given a great support, expecting the same till the end.

Hello Sahithi!  I'm very excited to have you joining our community!

> In my experience, this community is very supportive, patient, and
> friendly.  I’m sure you will find the same.  I’m looking forward to
> working with you and hope you’ll enjoy the experience.  Feel free to ask
> questions by sending email to guix-devel@gnu.org — chances are that
> someone else has the same question but didn’t dare to ask.

This has been my experience also.  I think "not being afraid to ask" is
one of the biggest challenges, in my experience, for students coming in
from Google Summer of Code or Outreachy.

Luckily you have a realy great mentor, and people here are generally
very happy to answer questions!

> To the rest of the Guix community: please welcome Sahithi and support
> this project by answering questions on IRC or here on the list.

Horray!  Welcome!  (Wait, I already said that, but welcome again!)

> I should add that Sahithi will be working on the project “Improve the
> user experience for the "guix package" command line tool”, which will
> address some of the major and minor problems that the command line
> interface currently has.  I’m the primary mentor for this project, and
> Gábor has volunteered to be co-mentor.  Thank you, Gábor!

Oh!  This is very exciting!

RE: 01/01: gnu: fftw: Build SIMD codelets.

[Eric Bavier]

Hi Mark,

> -Original Message-
> From: Mark H Weaver [mailto:m...@netris.org]
> Sent: Thursday, May 03, 2018 6:26 PM
> To: Eric Bavier
> Cc: guix-devel@gnu.org
> Subject: Re: 01/01: gnu: fftw: Build SIMD codelets.
> 
> Hi Eric,
> 
> ericbav...@centurylink.net (Eric Bavier) writes:
> 
> > bavier pushed a commit to branch core-updates in repository guix.
> >
> > commit 65bb22796f854cbc3eae053a80b1d64365dad376
> > Author: Eric Bavier 
> > Date:   Fri Apr 6 10:53:06 2018 -0500
> >
> > gnu: fftw: Build SIMD codelets.
> >
> > * gnu/packages/algebra.scm (fftw)[arguments]: Remove 'no-native
> phase; use
> > configure cache value instead.  Add configure flags for SIMD codelets.
> > (fftwf)[arguments]: Add neon configuration flag for 32-bit arm.
> > (fftw-avx): Remove variable.
> 
> [...]
> 
> > @@ -560,7 +569,10 @@ cosine/ sine transforms or DCT/DST).")
> >  (arguments
> >   (substitute-keyword-arguments (package-arguments fftw)
> > ((#:configure-flags cf)
> > -`(cons "--enable-float" ,cf
> > +(if (string-prefix? "arm" (or (%current-target-system)
> > +  (%current-system)))
> > +`(cons "--enable-neon" ,cf)
> > +cf
> 
> Did you intend to remove the "--enable-float" configure flag in fftwf?
> You didn't mention this change in the commit log.

Indeed, I think this was unintentional.

> Can you take a look?

Yes, thanks for checking.

`~Eric

Re: Packaging a free Firefox

[Pjotr Prins]

On Thu, May 03, 2018 at 01:59:24PM -0400, Mike Gerwitz wrote:
> I use IceCat personally and FF Dev Edition at work.  Until the recent
> move to WebExtensions, I used the same addons.  I use NoScript and Tor
> and have no problems.  But I rarely enable JS and never run proprietary
> JS, so my exposure may be different.  I do not use LibreJS (because I
> don't usually run JS at all in general and it historically did not play
> well with NoScript; maybe that has changed).

Disabling all extensions makes Icecat work much better. I'll try it as
a default now.

Question: why do we switch on extensions by default? Sure confused my
experience.

Pj.

Re: GSoC: Adding a web interface similar to the Hydra web interface

[Ludovic Courtès]

Hello Tatiana,

Tatiana Sholokhova  skribis:

> I'm Tatiana, I'm a GSoC intern. Now, I'm pursuing my master degree
> in Computer Science at Moscow State University.
>
> My project in GSoC is implementation web interface analogous to Hydra
> interface.

Thanks for your message, and welcome to Guix!

A good starting point for you will be to take a look at the basic ideas
behind Cuirass: what it does, how it structures information about builds
that it performs (which can be inferred from its database¹).

In terms of Web interface, Danny Milosavljevic wrote a simple HTML page
with JavaScript code that queries Cuirass using its HTTP interface².
You can see it here:

  https://berlin.guixsd.org/status/

It’s rough on the edges but it gives you an idea.

Anyway, these are the entry points.  Please do get in touch with us as
you start digging into it.  People on the mailing list and on IRC can
help (I’m “civodul” on IRC.)

Happy hacking!  :-)

Ludo’.

¹ https://git.savannah.gnu.org/cgit/guix/guix-cuirass.git/tree/src/schema.sql
² 
https://git.savannah.gnu.org/cgit/guix/guix-cuirass.git/tree/src/cuirass/http.scm

GSoC project ``Syntax and semantics of systemd units in the Shepherd''

[Ioannis Panagiotis Koutsidis]

Dear all,

I am Ioannis Panagiotis Koutsidis (Rukako on #guix) and I was selected
for the ``Syntax and semantics of systemd units in the Shepherd'' GSoC
2018 project.

I am looking forward to working with you, please feel free to email me
or beep me at IRC at any time.


0x0C8877F4.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: 29/88: gnu: Add emacs-let-alist.

[Pierre Neidhardt]

Sorry, you are absolutely right.  There are two mpv packages which names
were counter-intuitively swaped.

So `emms-player-mpv` is the one that was integrated in Emms 5.0.
`emms-player-simple-mpv` is the more complete, IPC mpv-based player.

Note that work in being done on the Emms mailing list to integrate the
IPC version, either from the -simple-mpv package or from original work.

--
Pierre Neidhardt

Avoid Quiet and Placid persons unless you are in Need of Sleep.
-- National Lampoon, "Deteriorata"


signature.asc
Description: PGP signature

Re: 29/88: gnu: Add emacs-let-alist.

[Oleg Pykhalov]

Hello Pierre,

Pierre Neidhardt  writes:

[…]

> Wow, impressive work indeed.  Note that you shouuld not have added
> emms-player-simple-mpv since it's superseded by Emms 5.0.

Do you mean ‘emms-player-simple.el’ from:
--8<---cut here---start->8---
tar xf $(~/src/guix/pre-inst-env env GUIX_PACKAGE_PATH= guix build --no-grafts 
-S emacs-emms) emms-5.0/lisp/emms-player-simple.el
--8<---cut here---end--->8---

I didn't check it carefully, but as I see it's not the same because I
don't see ‘json’ mentioned anywhere.  Also ‘cloc’ tells about 1936 lines
of Lisp code in ‘emms-player-simple-mpv’.  I will try ‘emms’ 5.0 later.

> I'll take care of this in a few days unless someone is faster than me :)

OK, thank you!  But please make sure that ‘emms-player-simple.el’ from
Emms is really the same as ‘emms-player-simple-mpv’, which uses MPV IPC
and parses JSON (not just starts a ‘mpv’ process per song or video).

Oleg.


signature.asc
Description: PGP signature