Re: warning: could not locate elisp directory under `/gnu/store/...`

[Alex Kost]

Pierre Neidhardt (2018-04-08 22:27 +0530) wrote:

Hello, Pierre!

> I'm down to write my first Emacs package declaration (attached).
> It seems quite straightforward and yet it fails to byte-compile:
[...]
> What am I missing?

Probably nothing.  I have just tried your package recipe and *.el files
have been successfully compiled for me (on the latest guix checkout).  I
noticed there were multiple changes in the 'emacs-build-system' lately,
so perhaps you just tried to build your package in a "wrong" time :-)

So I think your package is OK.  Could you just do "guix pull" and
rebuild it?

-- 
Alex

Re: Blog team

[Pierre Neidhardt]

Ricardo Wurmus  writes:

>> I recently had a fair discussion over Guix vs. NixOS vs. the world:
>>
>>  
>> https://www.reddit.com/r/emacs/comments/8a94rt/helm_system_packages_update_guix_xbps_void_linux/
>
> Here’s another one for reference in response to the question “What are
> the advantages of guix vs nix?”:
>
> https://news.ycombinator.com/item?id=16491797

Great write up!  And great post too :)

-- 
Pierre Neidhardt

 wow, I think I just used libtool to solve a problem -- somebody
help me! :>
 xtifr, STEP AWAY FROM THE KEYBOARD


signature.asc
Description: PGP signature

Re: Blog team

[Ricardo Wurmus]

Hi Pierre,

> I recently had a fair discussion over Guix vs. NixOS vs. the world:
>
>   
> https://www.reddit.com/r/emacs/comments/8a94rt/helm_system_packages_update_guix_xbps_void_linux/

Here’s another one for reference in response to the question “What are
the advantages of guix vs nix?”:

https://news.ycombinator.com/item?id=16491797

> One of the hottest topic that I'm tackling at the moment is the
> management of non-opensource installs. […]
> Not completely sure that would fit a Guix blog entry though :p

Yeah, I think this should not be published on the official project blog,
as non-free software really is out of scope for our project.

--
Ricardo

Re: Blog team

[Pierre Neidhardt]

Very nice initiative!

I'd be very happy to share some ideas on this blog, but I still have to
put my things together.

I recently had a fair discussion over Guix vs. NixOS vs. the world:


https://www.reddit.com/r/emacs/comments/8a94rt/helm_system_packages_update_guix_xbps_void_linux/

Lots of interesting points where raised I think.

One of the hottest topic that I'm tackling at the moment is the
management of non-opensource installs.  This is relevant to gamers in
particular since the gaming industry is still wary of committing to the
open source development model, even among the more "open" actors (Steam,
GOG.com, Humble Bundle).

This is a far cry to the game devs: binaries are not sustainable,
reproducible builds are an ever pressing call for opensource releases.

Some points would include:

- Binary patching (RPATH and ld interpreter)
- The multilib hassle (32-bit on 64-bit systems)
- Static linking vs. dynamic linking.

Not completely sure that would fit a Guix blog entry though :p

--
Pierre Neidhardt

As a goatherd learns his trade by goat, so a writer learns his trade by wrote.


signature.asc
Description: PGP signature

Re: Multilib support: running 32-bit binaries on 64-bit systems

[Ludovic Courtès]

Pierre Neidhardt  skribis:

> Guix already supports cross-compilation out of the box of 32-bit
> packages on any architecture:
>
>   guix build --system=i686-linux PACKAGES...

Just a note: this is native compilation, *not* cross-compilation.
x86_64 machines can run i686 binaries, which is why the above command
works just fine.

For cross-compilation, see ‘--target’.

Ludo’.

Re: Multilib support: running 32-bit binaries on 64-bit systems

[Ludovic Courtès]

Marius Bakke  skribis:

> One alternative would be to create a 32-bit profile, and set up
> FHS-style symlinks for it (or a chroot).  I've been thinking about
> adding a "--fhs" argument to `guix environment --container`, but it's
> still very much in the "dreaming" phase.

In the meantime one can use ‘guix environment -C --expose=…’ to expose
directories as /bin and the likes.

Ludo’.

Re: Cannot send patch.

[Ludovic Courtès]

Hi,

Fis Trivial  skribis:

> Chris Marusich writes:
>
>> Fis Trivial  writes:
>>
>>> It seems that I can't send anything to the patch mailing list in recent
>>> days. The last patch I sent is:
>>>
>>> http://lists.gnu.org/archive/html/guix-patches/2018-04/msg00116.html
>>>
>>> After that, I couldn't send mail to the list.
>>
>> I see an email from you a few days after that one:
>>
>> http://lists.gnu.org/archive/html/guix-patches/2018-04/msg00160.html
>>
>> Are you still having this problem?
>>
> That two mails are sent in the same day, check the date embedded in the
> link.
>
> I didn't try again lately. I will try to rebase the work on current
> master branch and then send the patch again once I have the time.

Please let us know if this is still broken for you.  Looking at

it seems that the mailing list is alive and well currently, so perhaps
we should investigate whether there’s something wrong with your own
messages.

Thanks,
Ludo’.

Re: Does Linux 4.16.1 blast out battery time? (9h+ -> 3h+)

[Ludovic Courtès]

Hello,

Pierre Neidhardt  skribis:

> With a bit of tweaking, I figured that enabling power management on
> on "Audio codec":
>
>   echo '1' > '/sys/module/snd_hda_intel/parameters/power_save';
>
> helped a little bit.  But not that much.  Now on 4.14.33, I get 10h,
> while on 4.16.1 I get 5h.
>
> There is something else.

That sounds worrying.  Could you report it upstream?

> By the way, how do I make the above /sys/ tweak permanent on GuixSD?

You could do something like:

  (simple-service 'my-/sys-tweaks activation-service-type
  #~(call-with-output-file "/sys/…"
  (lambda (port)
(display "1" port

That said, we should probably build a higher-level
‘/sys-tweaks-service-type’ where we could directly pass pairs of file
name/values.

Would you like to give it a try?

Thanks,
Ludo’.

Re: `guix package -u` upgrades packages to themselves

[Ludovic Courtès]

Hello,

Pierre Neidhardt  skribis:

> Sorry if I was confusing:  the output remains the same after upgrade.

There’s also one case that’s currently handled suboptimally: packages
with propagated inputs are systematically upgraded.  See
.

Clearly we should do better, probably by recursively checking whether
said propagated inputs would be upgraded.

Ludo’.

Re: Multiple pulseaudio process after re-loging

[Pierre Neidhardt]

I'm not doing anything to start Pulseaudio since it starts
on demand.  I can't think of anything wrong with how I start my
user session.  I run EXWM via ~/.xsession.  See my dotfiles:

https://github.com/ambrevar/dotfiles

Find my config.scm attached.

-- 
Pierre Neidhardt


config.scm
Description: Binary data


signature.asc
Description: PGP signature