Updating mono. Adding MSBuild.
Hi all, Our mono package is pretty severely out of date. I want to take care of updating it to a version consistent with this century. However, there seems to be an issue perhaps along the lines similar to bootstrapping Rust and JDK. Mono, for most distributions, seems to be bootstrapped with a prebuilt binary mono-lite. Due to this, I am unsure of how to make the first step in correctly repackaging Mono. Additionally, this should ideally come with the newer MSBuild, which Nix currently lacks. It is included in the Mono source tree, but I would assume we would want that to be separated and rather called by a propagated/native input? Anyways, a lot to unpack here. I'd appreciate any help I could get. Best, Brett Gilio
Re: Declarative containers
Hello, thanks for your feedback Ludo'! :-) Ludovic Courtès writes: [...] > Given that we already have ‘guix system container’, declarative > containers are a low hanging fruit. "low hanging fruit" is much more expressive than "last mile" :-) > We could have a ‘container’ (or ‘sub-system’?) service; mumble: `container` is so abused that it's starting to become a buzzword to my ears, `sub-system` is probably more semantic > you’d pass it an and it’d create a Shepherd service > that runs that OS in a container. what is the method used to instantiate containers with Guix? I know lxc/lxd and systemd-nspawn but can't still understand what's used here > That would be fun! yep, a *lot* of fun also, given Guile homoiconicity a web based (who wants web based interfaces?!? bah?) and/or declarative orchestration system built on top of Guix+GWL would be the next (not so low) hanging fruit :-D uh, if only I was able to hack in guile... I'll get there but I'm so sorry I cannot help _now_ :-S Gio'. -- Giovanni Biscuolo Xelera IT Infrastructures signature.asc Description: PGP signature
Re: 06/15: gnu: wesnoth-server: Rename package to the-battle-for-wesnoth-server.
Hello, On Tue, Mar 26, 2019 at 04:32:46PM +0100, Pierre Neidhardt wrote: > Sorry, I misunderstood the conclusion of the discussion: I thought that > we would simply follow the package naming convention as per the manual. I am confused about this statement. The naming convention speaks a bit vaguely of "project name chosen upstream"; very often, this means the tarball name. Now there is www.wesnoth.org, which distributes tarballs and executable files called wesnoth.*. So I would argue that the upstream name is "wesnoth" and would suggest to revert this change. This is in a similar spirit to "gcc" for instance; we do not call it "gnu-compiler-collection" either, although this is the long name used on their project web page. Andreas
Re: Video narration
Hi Paul! > I have found that the flickering is caused by the change in aspect > ratio as the video moves from the slide view to the screen view (and > back). Parole and Videos have a default 'Auto' setting for aspect > ratio that re-sets the aspect ratio during playback. If I change to a > constant aspect ratio (4:3, for example) the flickering stops. Great thank you! > > Is this something that you could look into? Sure! But I am struggling with finishing the audios now. I have just pushed the cli sessions for the first video. Believe me that they take long. Promise to check this after that. Regards and thank you for your finding :) Laura
Re: Audio/sound (ALSA) in guix environment --container
Ludovic Courtès writes: > I’m thinking we should change ‘guix environment -C’ to map to a UID > other than zero, at least by default. When developing code, some tools > may behave differently when running under UID 0 and that’s rarely what > we need I think. Thoughts? I agree. Defaulting to UID 0 is not good. (“conda” is an example of one application that has very different behaviour when it thinks it is running as root.) -- Ricardo
Declarative containers
Hello, Giovanni Biscuolo skribis: > having that, the "last mile" in *obsoleting* tools like Docker & > Co. (e.g. kubernetes, even openstack probably) is to have a declarative > way to setup containers, something like `containers.` from NixOS > [1] [...] > [1] https://nixos.org/nixos/manual/index.html#sec-declarative-containers Given that we already have ‘guix system container’, declarative containers are a low hanging fruit. We could have a ‘container’ (or ‘sub-system’?) service; you’d pass it an and it’d create a Shepherd service that runs that OS in a container. That would be fun! Ludo’.
Re: Video narration
Hi Laura, > If others could test with their own players that may give us clue. > Sure, as many players, the better. I have found that the flickering is caused by the change in aspect ratio as the video moves from the slide view to the screen view (and back). Parole and Videos have a default 'Auto' setting for aspect ratio that re-sets the aspect ratio during playback. If I change to a constant aspect ratio (4:3, for example) the flickering stops. The snag with a constant aspect ratio is that one or other of the views then looks stretched. Padding on the left and right of the screen view might be the best fix. Then the two views could share the same aspect ratio. Is this something that you could look into? Best regards, Paul.
Re: Audio/sound (ALSA) in guix environment --container
Hello! Pierre Neidhardt skribis: > I'm trying to run an graphical application with audio in a Guix > environment. > > So far: > > guix environment --container \ > --share=/tmp/.X11-unix/ \ > --share=/dev/snd \ > --ad-hoc foo coreutils -- \ > env DISPLAY=$DISPLAY foo "$@" > > > I get this error: > > ALSA lib pcm_direct.c:1943:(snd1_pcm_direct_parse_open_conf) The field > ipc_gid must be a valid group (create group audio) > > > I though --share=/dev/snd would help, but I don't think that's useful. > I tried creating the "audio" group in the container or adding the user > to the group, to no avail: > >> guix environment -C --ad-hoc coreutils shadow > ambrevar@bababa . [env]# groups > groups: cannot find name for group ID 0 > 0 groups: cannot find name for group ID 65534 > 65534 Commit 952afb6f8c209692e52f9561965ee39e143e1d88 changes ‘guix environment’ so that it creates /etc/group, using the brand new (gnu build accounts) module. Now ‘id’ and ‘groups’ work fine in containers. Does it solve the specific problem you were having? Maybe there are other things that would need to be done, dunno. I’m thinking we should change ‘guix environment -C’ to map to a UID other than zero, at least by default. When developing code, some tools may behave differently when running under UID 0 and that’s rarely what we need I think. Thoughts? Ludo’.
Re: wip-netlink
Hi Gábor, Gábor Boskovits skribis: > I've pushed a branch with some preliminary work on the netlink wrapper > for guix, so that > we can have ipv6 static network configuration, and a bunch of other > goodies, including hopefully container networking. > This is in quite an early stage, I was mostly doing some research, and > tried to define the data structures needed. > Wdyt? I think it looks like a great start! Then you’ll need to provide bindings to ‘sendmsg’ to actually make use of the data structures you defined (Guile itself already provides ‘sendmsg’ but it’s too high-level to be usable with netlink sockets, AFAICS.) We can chat on IRC if you have any questions or comments. Thank you for working on it! Ludo’.
Re: 06/15: gnu: wesnoth-server: Rename package to the-battle-for-wesnoth-server.
Tobias Geerinckx-Rice writes: > guix-comm...@gnu.org wrote: >> gnu: wesnoth-server: Rename package to >> the-battle-for-wesnoth-server. > > My fault for totally missing the review window, These changes were not submitted as patches, so there was no review window. It would have been better to find consensus first. -- Ricardo
Re: 06/15: gnu: wesnoth-server: Rename package to the-battle-for-wesnoth-server.
Pierre, guix-comm...@gnu.org wrote: gnu: wesnoth-server: Rename package to the-battle-for-wesnoth-server. My fault for totally missing the review window, but could we at least drop the articles from the-long-package-names before they become too widespread? (I'll defer to you on l-abbaye, tho'.) Kind regards, T G-R signature.asc Description: PGP signature
Re: Package file indexing
Pierre Neidhardt skribis: > Ludovic Courtès writes: [...] >> The daemon could have a special RPC: you give it a file name and it >> returns a store item (or package+version?) or #f. > > I think you meant "store itemS" (plural), no? Yes. >> Internally it’d call ‘guix substitute’ to fetch the file index from >> the substitute server, check its signature, cache it locally, and then >> look up the file. >> >> You should look at how NixOS does it for its ‘command-not-found’ support >> (I think it’s part of NixOS, not Nix). IIRC they distribute an SQLite >> database, but it’s a pretty ad-hoc mechanism without authentication. > > I could work on this, but that seems like a lot of work, especially for > me who knows nothing about the daemon (but hey, it's a great opportunity > to learn!). Note that the daemon would act as an intermediary, but in practice the functionality would be very much peripheral to the daemon. IOW, you don’t need to know about the daemon internals. Ludo’.
