Re: Zotero Packaging Request

Hello Ludo! Thanks for the information. Sure, I will definitely try packaging some apps. I needed to ask someone this time as I preoccupied with writing a book and planning to be published under GNU Press. It's involves free software and guix. So it would be helpful if someone could cover for t

Re: 04/04: gnu: dropbear: Don't use unstable tarball.

guix-commits wrote: nckx pushed a commit to branch master in repository guix. commit 40d59c4e22c217e1f9215056b8b5977a6352239c Author: Tobias Geerinckx-Rice Date: Thu Mar 28 20:14:36 2019 +0100 gnu: dropbear: Don't use unstable tarball. * gnu/packages/screen.scm (dropbear)[source

Re: 01/01: build-system/ruby: Use invoke.

On Thu, Mar 28, 2019 at 06:14:48PM +, Christopher Baines wrote: > > guix-comm...@gnu.org writes: > > > efraim pushed a commit to branch staging > > in repository guix. > > > > commit 0244952c11c0409597fce5c39dfbcafdfd2ea651 > > Author: Efraim Flashner > > Date: Thu Mar 28 19:17:34 2019 +02

Re: 01/01: build-system/ruby: Use invoke.

guix-comm...@gnu.org writes: > efraim pushed a commit to branch staging > in repository guix. > > commit 0244952c11c0409597fce5c39dfbcafdfd2ea651 > Author: Efraim Flashner > Date: Thu Mar 28 19:17:34 2019 +0200 > > build-system/ruby: Use invoke. > > * guix/build/ruby-build-system.scm (

New German PO file for 'guix-manual' (version 0.16.0.1)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'guix-manual' has been submitted by the German team of translators. The file is available at: https://translationproject.org/latest/guix-manual/de.po (We can arrange things

Re: Packaging for guix

Hi Ricardo, Thanks. I've been hacking in my channel and master usually has my current work: https://github.com/jsoo1/guix-channel/blob/master/python-pyside.scm - current commit is 59f6da3. Aside - I would like

Re: Status update on 1.0

Ludovic Courtès writes: > Hello Guix! > > When we said we’d try to release 1.0 for FOSDEM, we were talking about > FOSDEM *2019*, which is well over now, so I think we need to get our act > together and complete the remaining tasks for 1.0. :-) On the plus side, we still have a lot of time left

Re: XDG_DATA_DIRS issue in execution environment on LTSP

Hi, Meiyo Peng writes: > #+begin_src fish > if status is-login || status is-interactive > set -gx MY_PROFILE "$HOME/.guix-profile" > > # Guix on foreign distros. > # This test is a dirty hack. > if test -d /var/guix && ! test -L /run/current-system > # Environm

Re: XDG_DATA_DIRS issue in execution environment on LTSP

Hi Giovanni, Giovanni Biscuolo writes: >> #+begin_src fish >> if status is-login || status is-interactive >> set -gx MY_PROFILE "$HOME/.guix-profile" >> >> # Guix on foreign distros. >> # This test is a dirty hack. >> if test -d /var/guix && ! test -L /run/current-system

Re: XDG_DATA_DIRS issue in execution environment on LTSP

Hi Giovanni, Giovanni Biscuolo writes: > I want to share this issue and show my "workaround" to fix it, please > send your comments on alternative ways or other caveats you may find in > my reasoning Thank you for sharing you experience with us. > I'm running Guix on top of Debian/stretch, rece

Re: XDG_DATA_DIRS issue in execution environment on LTSP

Hi Meiyo, Meiyo Peng writes: [...] > According to the XDG Base Directory Specification [1]: > > #+begin_quote > If $XDG_DATA_DIRS is either not set or empty, a value equal to > /usr/local/share/:/usr/share/ should be used. > If $XDG_CONFIG_DIRS is either not set or empty, a value equal to

Re: Packaging for guix

[- pyside] Hi John, > I’ve tried using the provided python build process but I get several > build errors, let alone runtime issues. Would anyone be able to point > me in a direction to patch pyside for such a packaging system? > Currently I’m stuck building Shiboken. I’d particularly like guidan

Re: create a symlink

Hello Danny, Danny Milosavljevic writes: > > In that case, /hurd could be handled like we handle /run/booted-system . > As I understand Guix, /run/booted-system is created during the boot(activation) process; however, I think that to perform the activation there should already be /hurd (binari

Re: 05/15: gnu: wesnoth: Rename package to the-battle-for-wesnoth.

Pierre Neidhardt writes: >> The package name is just an identifier for command line interaction >> purposes. > > I don't see it this way. The package name is a global variable in the > Guix project, and it bears a global semantic value. It's used as a > public identifier that has to meaningfu

Re: 05/15: gnu: wesnoth: Rename package to the-battle-for-wesnoth.

Ricardo Wurmus writes: > Let’s fix that then and make it faster. (I think it’s pretty good > already and it’s how I find packages, not by trying out names.) The user experience I'm talking about is, well, the opposite: not to try out names. But maybe this is hard to communicate over emails for