Re: [GNU-linux-libre] [PATCH] gnu: Add ungoogled-chromium.

On 02/07/2019 06:52 PM, Christopher Lemmer Webber wrote: > Ludovic Courtès writes: > >> Hi bill-auger, >> >> bill-auger skribis: >> >>> re: https://lists.gnu.org/archive/html/guix-devel/2019-02/msg9.html >>> >>> i would like to remind readers of the guix-devel list that it was >>> discussed

Re: [PATCH] gnu: Add ungoogled-chromium.

Ludovic Courtès writes: > Hi bill-auger, > > bill-auger skribis: > >> re: https://lists.gnu.org/archive/html/guix-devel/2019-02/msg9.html >> >> i would like to remind readers of the guix-devel list that it was >> discussed some months ago, why no FSDG distros currently distribute >>

News from the Guix Days!

Hello Guix! Efraim kindly wrote about a session he participated in at the Guix Days: https://gnu.org/software/guix/blog/2019/qa-on-non-intel-at-guix-days/ Congrats on fixing Go on ARM! \o/ I’d like to invite the other participants :-) to either prepare a Markdown-formatted summary of their

Re: Video documentation repository

Hello! Björn Höfling skribis: > On Tue, 05 Feb 2019 00:02:20 +0100 > Ludovic Courtès wrote: > >> Great initiative! I can’t create it myself but I’ve filed a support >> request: (the Savannah >> hackers usually respond within a couple of days.) > >

Re: Spliting a huge package

Hartmut Goebel transcribed 2.5K bytes: > Hi, > > following up a discussion from the GNUne mailinglist about how to slice > the software, I would like to learn about the best practice of packaging > huge packages in guix. > > Assume gnuet will be delivered a one big TGZ, inclusing base-libs, >

Re: New videos: topic daily use.

Laura Lazzati writes: > On Wed, Feb 6, 2019 at 7:17 PM Ricardo Wurmus wrote: > >> > I was thinking of daily use of guix package, mentioning profile, >> > generations (both the concepts and commands to deal with them) >> >> Sounds good. “--install”, “--roll-back”, and maybe even “--manifest”

Re: New videos: topic daily use.

Hi! On Wed, Feb 6, 2019 at 7:17 PM Ricardo Wurmus wrote: > > I was thinking of daily use of guix package, mentioning profile, > > generations (both the concepts and commands to deal with them) > > Sounds good. “--install”, “--roll-back”, and maybe even “--manifest” > for stateless installations

Spliting a huge package

Hi, following up a discussion from the GNUne mailinglist about how to slice the software, I would like to learn about the best practice of packaging huge packages in guix. Assume gnuet will be delivered a one big TGZ, inclusing base-libs, core-services, additional-services, guis for services.

Change syntax of '--with-source' flag to match syntax of '--with-commit' flag?

The '--with-commit' flag changes the source used to build a package, the syntax takes the form of '--with-commit=='. The '--with-source' flag also changes the source, but uses the syntax '--with-source=', but only transforms the top-level package (e.g. `guix build ` or `guix environment

Re: Policy to remove obsolete packages

Hi, I understand but I am not sure to see the points and/or advantages about a policy. >From my opinion, obsolete package is not well-defined and define cleanly what an obsolete package is will be bikeshedding. :-) And I think that deprecated should come from upstream. However, a popcon of the

Re: Policy to remove obsolete packages

swedebugia writes: > I like the idea of keeping it simple and now we tried the lumped > modules approach. I don't like it so much to be honest. > > It comes with obvious drawbacks when the package per file grow and > subcategorization have to be done. > > But is it efficient in guile to load

Re: 02/04: monads, gexp: Prevent redefinition of syntax parameters.

guix-comm...@gnu.org writes: > civodul pushed a commit to branch master > in repository guix. > > commit 8245bb74fc7bdcdc2f9d458057cefc9cd982e489 > Author: Ludovic Courtès > Date: Wed Feb 6 21:58:43 2019 +0100 > > monads, gexp: Prevent redefinition of syntax parameters. > > Fixes