Should python-build-system packages have native-inputs?

Hi Guix, I've noticed that a fair number of packages in gnu/packages/python.scm using the python-build-system declare native-inputs. I suspect that in every case, these should actually just be inputs. I also suspect that this is benign, except perhaps for the fact that it may confuse

Re: Should python-build-system packages have native-inputs?

Chris Marusich writes: > Hi Guix, > > I've noticed that a fair number of packages in gnu/packages/python.scm > using the python-build-system declare native-inputs. I suspect that in > every case, these should actually just be inputs. I also suspect that > this is benign, except perhaps for the

Re: Should python-build-system packages have native-inputs?

Am 28.04.2018 um 08:50 schrieb Chris Marusich: > * Should we change these native-inputs to inputs to prevent confusion? > I can personally vouch for the fact that the presence of native-inputs > in python-build-system packages confused the heck out of me at first!   As Fis already wrote: 

Re: Should python-build-system packages have native-inputs?

Hi Fis and Hartmut, Thank you for the quick response! Hartmut Goebel writes: > As Fis already wrote:  These native-inputs are for testing and shouldn't > be installed in normal case. It's true that for some of the packages that use the python-build-system, we

Re: Should python-build-system packages have native-inputs?

Am 28.04.2018 um 12:11 schrieb Chris Marusich: I understand your concerns, and I understand why this is hard to get for a Pythonista. But this is exactly why we added this section to the manual. > Because the python-build-system never cross-compiles, This is an implementation detail which

Mes 0.13 released

I am pleased to announce the release of Mes 0.13, representing 45 commits over 3 weeks. MesCC can now compile a functional tcc when running on Mes (in ~1h45') or on Guile (in ~3min). This means that we are getting very close to a full source bootstrap of tcc: it is now built without gcc, glibc

Re: GSoC-2018

Sandeep Subramanian writes: > Hi all, > > I am Sandeep Subramanian (uniq10) and I have been selected for the > GSoC-2018 project "Continue rewrite build daemon in Guile Scheme". > (Project description: >

New Spanish PO file for 'shepherd' (version 0.3.3-pre1)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'shepherd' has been submitted by the Spanish team of translators. The file is available at: http://translationproject.org/latest/shepherd/es.po (We can arrange things so

Rebasing guile-daemon branch onto master

Hi all, I was trying to rebase the guile-daemon branch onto the master branch and I have some trouble doing it. The interactive git rebase showed me that there are 932 commits to be picked but most of them had no relation to the daemon code (Most commits were package addition/update commits.) I

Re: Should python-build-system packages have native-inputs?

Hartmut Goebel writes: >> the python-build-system does not cross-compile. > > In any case, this is a current limitation only :-) I see. If we actually do plan on implementing some kind of cross-compilation support for the python-build-system, then I can understand

Re: Mes 0.13 released

Hi Jan, Jan Nieuwenhuizen writes: > I am pleased to announce the release of Mes 0.13, representing 45 > commits over 3 weeks. MesCC can now compile a functional tcc when > running on Mes (in ~1h45') or on Guile (in ~3min). That is absolutely awesome! My deepest, deepest

You say nix, I say guix: Nix 2.0 and Guix

Hi, On February 22nd, Nix 2.0 was released: https://nixos.org/nix/manual/#ssec-relnotes-2.0 It contains a lot of interesting new features. Are there any plans to merge some of the nix-daemon changes into our guix-daemon? Is compatibility with the nix-daemon a goal of the Guix project? Can we

Re: Rebasing guile-daemon branch onto master

> I was trying to rebase the guile-daemon branch onto the master branch > and I have some trouble doing it. > The interactive git rebase showed me that there are 932 commits to be > picked but most of them had no relation to the daemon code (Most commits > were package addition/update commits.) I

Re: GSoC-2018

Hi Sandeep/uniq10, welcome! I'm the person that worked on the rewrite last year (I like to go by reepca in conversations and irc). I'm glad that you'll be working on it this summer. I still feel like I didn't do enough last summer, though, so if there's any way I can help, I'd be glad to (though

Re: Rebasing guile-daemon branch onto master

On Sat, Apr 28, 2018 at 07:10:00PM +, Sandeep Subramanian wrote: > Shall I now rebase by picking only these 30 commits? > > I don't know if what I am doing is right. I could use some guidance and > criticism now. Yes, I think that picking only those 30 commits is the right thing to do.