IRC channel logs


back to list of logs

<civodul>Hello Guix!
<viric>bonjorn guix!
<civodul>i got negative feedback on how the web page and manual provide info for newcomers who want to add packages
<civodul>obviously i'm in a bad position to find out the problems and solutions :-)
<civodul>so i would appreciate if people have suggestions!
<nkar>civodul: which parts exactly are difficult to follow, according to the newcomer?
<civodul>nkar: finding the info on how to add a package to the distro, starting from
<civodul>honestly, i don't fully understand what was said
<nkar>there's a tutorial by a_e, doesn't it explain that?
<civodul>yes, it does
<civodul>the manual does as well, i think
<civodul>but maybe the info is burried, or badly structured
*civodul has to go
<nkar>we cannot find a solution if we don't understand the problem
<ph4nt0mas>hello guix
<sneek>Welcome back ph4nt0mas, you have 1 message.
<sneek>ph4nt0mas, civodul says: try running "make clean-go && make", to account for the recent ABI change
<alezost>civodul: hi, (derivation-outputs (package-source-derivation ...)) is always ⇒ (("out" . #<<derivation-output> ...>)). I mean there is always just "out" for a source derivation. Am I right?
<civodul>alezost: yes, there's always just one output
<civodul>i can't think of any reasonable use case where it'd be different
<alezost>civodul: great, thanks
<bavier>why would (eq? (package-source (@ (gnu packages commencement) gcc-boot0)) (package-source (@ (gnu packages gcc) gcc-4.8))) => #f if gcc-boot0 inherits from gcc-4.8?
<davexunit>are the `equal?'
<bavier>davexunit: no
<civodul>bavier: because of package-with-bootstrap-guile, which changes the <origin>
<civodul>so that it gets downloaded with the bootstrap guile
<civodul><origin> has a 'guile' field
<civodul>you may want to compare modulo that field
<bavier>civodul: I see, ok
<a_e>So a quick question I asked also on the mailing list:
<a_e>Where do I find the nix code for its kde build system?
<a_e>Their recipe for ktouch looks like this:
<a_e>kde { buildInputs = [ kdelibs libxkbfile ]; meta = { description = "Touch Typing Tutor"; }; }
<a_e>It looks like all the logic is in the first word...
<civodul>oh right, lemme see
<civodul>i don't even see that actually
<civodul>in a current Nixpkgs master
<a_e>You mean, you do not see the ktouch recipe?
<civodul>there's pkgs/desktops/kde-4.14/kde-package
<civodul>and part of it is generated
<civodul>apparently the guts are kde-package/default.nix, but it's a bit hard to read
<a_e>I do not see anything cmake related that could be of interest to us.
<civodul>me neither
<viric>because cmake is so easy that it doesn't need anything in particular
<a_e>I also looked into pkgs/development/tools/build-managers/cmake/default.nix.
<a_e>There I see CMAKE_PREFIX_PATH = stdenv.lib.concatStringsSep ":" buildInputs;
<a_e>which we cover by setting CMAKE_LIBRARY_PATH and CMAKE_INCLUDE_PATH CMAKE_INCLUDE_PATH separately.
<a_e>Nothing about linking.
<civodul>see also the bug iyzsong reported