IRC channel logs


back to list of logs

<civodul>Hello Guix!
<Steap>4pm, seems like Guix overslept
<civodul>it's cold and cloudy today, otherwise i'd be away
<Steap>Are you implying that Guix will be released faster if we have shitty weather ?
<civodul>could be ;-)
<jmd>It's sunny here.
<jmd>civodul: Regarding your review of my patch ...
<jmd>Those libraries are named by upstream with upper case. I thought we followed the upstream naming verbatim?
<civodul>jmd: yes.. except for case and dashes :-)
<jmd>Is that documented somewhere?
<civodul>see "Package Naming" in the manua,
<civodul>the part about dashes is not mentioned, i'll add it
<jmd>This policy complicates the formation of the url!
<jmd>I can no longer say (uri (string-append
<jmd> "mirror://gnome/sources/" name "/" (string-take version 3) "/" name "-"
<jmd> version
<jmd> ".tar.bz2"))
<jmd>Can we leave the name as original, but the public definition in lower case?
<taylanub>how do I get the manuals in $guix_profile/share/info listed in the (dir) page? looks like $guix_profile/share/info/dir is missing
<grasshopprWhoppr>jmd, is there a tolower() function?
<jmd>grasshopprWhoppr: That wouldn't help.
<jmd>I would need a to-how-it-was-in-the-first-place function.
<taylanub>oh, after a 'guix package -u' I have a dir file, but from glibc ..
*grasshopprWhoppr thought how it was (uppercase) was the opposite of what you needed, jmd.
<jmd>the problem is that the original string is mixed case.
<grasshopprWhoppr>so you need a hyphen @ every cap?
<grasshopprWhoppr>Why would mixed case be a problem for a tolower function if you only need a lowercase name? If you need to revert the name, can't you store it in a variable and then call that variable later?
<jmd>I suppose I could but that would make it even more complicated.
<civodul>taylanub: yes, 'dir' files are yet to be correctly handled...
<civodul>jmd: i think it's better to stick to a clear rule, otherwise it's going to be messy
<jmd>Would cividul be happy if I wrote (name (tolower "libIDL")) ? I don't think so.
<civodul>repeating the name in the URL is fine, i think
<civodul>just (name "libidl")
<civodul>case-mapping is done at packaging time :-)
<jmd>We need an (upstream-name "...") field.
<jmd>how many packages in guix these days?
<taylanub>tub@taylan:~$ guix package -A | wc -l
<zerwas>I read 742
<jmd>I think taylanub's number is in the latest release.
<jmd>(my local repo has 767)
<taylanub>oh, one doesn't get new packages until one updates guix, right? will we have a package DB eventually like other package managers tend to have?
<civodul>taylanub: you're supposed to run "guix pull" to receive updates
<civodul>it essentially does "git pull && make install", conceptually
<civodul>the "DB" is a set of modules, you know :-)
<jmd>civodul: That makes sense. However, it begs the question : what purpose does a Guix "release" serve?
<civodul>jmd: currently it's more of a milestone, as i view it
<civodul>because there are still fundamental things that are evolving
<civodul>eventually, when the base has become more stable, it'll be pretty much like for other distros: a way to mark a stable point in time
<civodul>but yeah, we'll see