From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tanguy Le Carrour Subject: Re: Problem with `direnv` package definition Date: Tue, 23 Apr 2019 22:34:53 +0200 Message-ID: <20190423203453.c3wfhzde4dncufxt@melmoth> References: <20190420132019.priud6wucj5l2rn6@melmoth> <87o950txsa.fsf@cbaines.net> <20190421083426.6snly2v4xmlneb32@melmoth> <87mukju1is.fsf@cbaines.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([209.51.188.92]:39157) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hJ28T-0008B5-TY for guix-devel@gnu.org; Tue, 23 Apr 2019 16:35:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hJ28P-0008Mz-JE for guix-devel@gnu.org; Tue, 23 Apr 2019 16:35:23 -0400 Received: from relay2-d.mail.gandi.net ([217.70.183.194]:34799) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hJ289-00085b-KB for guix-devel@gnu.org; Tue, 23 Apr 2019 16:35:09 -0400 Content-Disposition: inline In-Reply-To: <87mukju1is.fsf@cbaines.net> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Christopher Baines Cc: guix-devel@gnu.org Le 04/21, Christopher Baines a écrit : > Tanguy Le Carrour writes: > > Le 04/20, Christopher Baines a écrit : > >> Tanguy Le Carrour writes: > >> > However, in the package definition [2], 3 Go packages are listed as > >> > "inputs" whereas they should be listed as "native-inputs". Is this > >> > correct? > >> That sounds right to me, although there have been issues with binaries > >> generated with Go […] > […] > So, in contrast to some other package management systems, the runtime > dependencies, or references of the output(s) in the case of Guix are not > explicitly set in the package definition. > > This is still something I have a little difficulty understanding, but > the inputs/native-inputs distinction is more about architecture than > runtime references. Ouch?! If you have difficulty understanding it, imagine for me! ^_^' > I've just pushed a commit that pulls in the relevant phase, and makes > the inputs, native-inputs [1]. With that change, the size of the package > does drop [2]. Thank you so much for that! > That's not to say that making the inputs, native-inputs in this case is > wrong, quite the opposite. […] Currently the direnv package is using the > gnu-build-system, as it's one of the older go packages in Guix, however > it does now pull in some phases from the go-build-system. > […] > Anyway, while the size of direnv should now be improved, there's still > more improvements to be made to the direnv package if you're interested! > I think it would be better to switch to using the go build system, and > the package in Guix is quite a few versions behind. So this might be something I could be investigating in a near future! But I guess I'll have to read some Go package definitions first… Which won't be a waste of time, for `fzf` is also written in Go! Regards -- Tanguy