Dear,
On Mon, 16 Nov 2020 at 01:54, Ryan Prior wrote:
> For example, `docker size python` shows a 171.4mb bundle size just for
How is the Docker image built?
> Python alone, while `docker images python:alpine` shows a 44.3mb
> system
Idem?
I agree with your argument, I am just wondering if a
Hello Christopher,
CC'ing Ludovic since they had that problem as well, so might be
interested in testing your solution.
Christopher Lemmer Webber writes:
[...]
> I figured out what was happening! The bug is *technically* in vc-mode.
> However, nontheless it manifested here...
>
> Here's what
Hi!
Tobias Platen writes:
> On Mon, 9 Nov 2020 22:13:52 +0100
> Tobias Platen wrote:
>
>> I checked out the wip-ppc branch which I compiled on my Talos II.
>
> Guix now runs and is able to download files and put them in the store.
>
> ./pre-inst-env guix download https://ftp.gnu.org/gnu/guix/gu
On November 15, 2020, raingloom wrote:
> Alpine already achieves an incredibly tiny install size by splitting
> packages into many outputs. We could and should do the same.
> As far as I know, they do not have parameterized packages.
I definitely support more package-splitting and dependency tree
Hello,
Yeeeho! I've installed Guix 1.2.0rc1 system on a KVM virtual machine.
1. Because of DHCP server is not exist on a network I cannot use TUI
installer.
When I installed via shell, I need manually stop “networking” service
with herd. Otherwise “ip address” shows “169.254.182.22/16” assign
On Sun, Nov 15, 2020 at 10:53:29PM +0100, Marius Bakke wrote:
> I have just installed a system using manual partitioning through the
> installer, with encryption. Everything worked like a charm.
>
> Can you provide more details about the steps you did to arrive at the
> error? And information ab
"pelzflorian (Florian Pelz)" writes:
> On Fri, Nov 13, 2020 at 06:07:32PM +0100, Ludovic Courtès wrote:
>> system installation:
>> […]
>>
>> https://alpha.gnu.org/gnu/guix/guix-system-install-1.2.0rc1.x86_64-linux.iso.xz
>
> Sorry for testing so late. For me the graphical installer cr
Hi Danny,
Sorry to be late.
On Wed, 04 Nov 2020 at 15:50, Danny Milosavljevic
wrote:
>> Some days ago, we discussed on #guix about releasing Docker images
>> ready-to-use. And you pointed your project:
>>
>> https://gitlab.com/daym/guix-on-docker/
[...]
> For the use case I'm using it fo
On Sun, 15 Nov 2020 21:46:58 +0100
Danny Milosavljevic wrote:
> Hi Ludo,
>
> nice feature!
>
> On Sun, 15 Nov 2020 17:33:28 +0100
> Ludovic Courtès wrote:
>
> > An important question: do we have examples of packages for which
> > we’d like to have parameters?
>
> For the embedded/flash rom s
Dear,
On Sun, 15 Nov 2020 at 21:46, Danny Milosavljevic
wrote:
> * Enable/disable building the documentation. I really don't need a 40 MiB
> manual stored onto a 16 MiB firmware flash chip. If that's better done as an
> extra output, fair enough.
Related (I hope) is: build packages with seve
Hi Ludo,
nice feature!
On Sun, 15 Nov 2020 17:33:28 +0100
Ludovic Courtès wrote:
> An important question: do we have examples of packages for which we’d
> like to have parameters?
For the embedded/flash rom side:
* Enable/disable building the documentation. I really don't need a 40 MiB
manua
On Fri, Nov 13, 2020 at 06:07:32PM +0100, Ludovic Courtès wrote:
> system installation:
> […]
>
> https://alpha.gnu.org/gnu/guix/guix-system-install-1.2.0rc1.x86_64-linux.iso.xz
Sorry for testing so late. For me the graphical installer crashes
when doing a Manual Partitioning with an e
An important question: do we have examples of packages for which we’d
like to have parameters? I’d grepped for “inherit” and that yields a
few potential candidates, but also maybe a few potential non-candidates.
Would this be a good fit for them?
I suppose Emacs would be an obvious candidate, w
Hi,
>> > guix pack guix -f docker -S /bin=bin \
>> >--entry-point="bin/guix-daemon --disable-chroot"
[...]
>> > Someone needs to try because the devil is in the details.
>>
>> I will try to give a try. If someone does not beat me.
>
> Please do.
I did and probably am lost in Docker det
Hi Pierre,
On Sun, 15 Nov 2020 at 18:44, Pierre Neidhardt wrote:
> For instance, what if we want to build "all packages without X support"?
> This means that the parameter must traverse all inputs recursively if we
> don't want to drag X indirectly.
It means: add this new ’optionally’ to all th
Hi Lduo,
On Sun, 15 Nov 2020 at 17:33, Ludovic Courtès wrote:
> That said, this message is about a possible implementation of package
> parameters, so here we go. :-)
Cool!
> To me the requirements for package parameters are:
>
> 1. it must be possible to discover them and choose them from
Fantastic!
One of the biggest struggle we had when discussing it was figuring out
what to do about parameter propagation across dependencies.
For instance, what if we want to build "all packages without X support"?
This means that the parameter must traverse all inputs recursively if we
don't wan
More in general, grepping for `--enable` or `--with` flags shows
a lot of potential packages (but also many false positives).
Nicolò Balzarotti writes:
> Neat! Thanks for working on it :)
>
>> An important question: do we have examples of packages for which we’d
>> like to have parameters? I’d
Neat! Thanks for working on it :)
> An important question: do we have examples of packages for which we’d
> like to have parameters? I’d grepped for “inherit” and that yields a
> few potential candidates, but also maybe a few potential non-candidates.
> Would this be a good fit for them?
What ab
Hello Guix!
For some time we’ve discussed ways to achieve “parameterized
packages”—packages where one can from the command line or from Scheme
configure optional build-time features, similar to Gentoo “USE flags”.
I still have mixed feeling about this feature: on one hand it can bring
much welcom
Hi Ludo.
On Fri, 13 Nov 2020 at 18:07, Ludovic Courtès wrote:
> In any case, please report success, failure, and annoyances in this thread.
Everything looks fine for me. Even the ’r-*’ packages are there.
It is not finished yet but I would like to have a script that check the
availability bui
On Sun, 15 Nov 2020 at 16:45, Pierre Neidhardt wrote:
> Good stuff!
I do not know but you aroused me about Geiser. ;-)
> Can you report your findings on the GitLab repo of emacs-guix?
I could. Even send a patch. :-)
Once the future of Emacs-Guix is a bit more clear.
All the best,
simon
On Sun, 15 Nov 2020 at 15:11, Pierre Neidhardt wrote:
> My bad, makes sense now.
If it makes sense…
>> Especially if
>>
>> (guix-eval-in-repl
>>"(guix-build \"nyxt\" \"--no-grafts\" \"--check\")")
>>
>> works fine.
>
> What do you mean with this part?
… I mean replace the current
Hi zimoun,
On Sun, 15 Nov 2020 14:02:04 +0100
zimoun wrote:
> In an ideal world, the first ’,a’ could provide hint for the module to
> ’,use’
There is no "the" module. Any number of modules could have your searched-for
symbol--and the procedures so found could do completely unrelated things.
zimoun writes:
>> Maybe a misunderstanding, but comint-mode is not the problem here, it
>> works very well indeed with big outputs.
>> Only Geiser chokes on it.
>
> I do not understand your point. ’guix-eval-in-repl’ is a wrapper around
> ’geiser-repl--send’ so it uses Geiser, isn’t it?
Oops, s
Hi Pierre,
On Sun, 15 Nov 2020 at 08:37, Pierre Neidhardt wrote:
> zimoun writes:
>
>> Could you try this and tell if Emacs hangs? On my laptop, the first
>> attempts are not so worse. M-x ielm
>>
>> --8<---cut here---start->8---
>> *** Welcome to IELM ***
Dear,
Preparing the online Guix Days, maybe this discussion is worth. It
echoes first with the talks “Guix compared to Nix” then with the recent
discussion about Emacs-Guix [1].
The topic is discoverability at the REPL level.
Well, I have a proposal draft «“guix repl” and beyond» that I never
On Tue, Nov 10, 2020 at 08:56:21PM +0100, Tobias Platen wrote:
> Hello,
>
> I've got the wip-ppc branch of Guix compiling unmodified on my Talos II.
> Since the POWER9 is backwards compatible with the PowerPC G4, it can run
> the existing bootstrap binaries for powerpc-linux. The binaries from
> h
28 matches
Mail list logo