<reepca>two of them, one which turned out to be provided by guile. string-tokenize, hidden away under "miscellaneous string operations" in the manual, and mount-points from (guix build syscalls), which used string-tokenize. But hey, at least I made something useful - "octal-escaped", in case mount points have spaces in the name.
<reepca>also, out of curiosity, what's the difference between /proc/mounts and /proc/self/mountinfo?
<civodul>reepca: i think the latter takes namespaces into account
<civodul>while the former is the global list of mount points
<rekado>bleh, using the latest sphinx didn’t help.
<rekado>same error: ‘! Package babel Error: You haven’t specified a language option.’
<rekado_>that’s okay because ‘system*’ takes just a bunch of strings, and (assoc-ref outputs "out") returns a string.
<adfeno>quiliro: Important note: rekado_'s (system* "ls") example is, of course a simple usage of (system* ...), however, Guile Scheme itself has procedures (like "commands" in GNU Bash, or "functions" in any language) to do the same as "ls".
<rekado>quiliro: when you’re done modifying the recipe for qscintilla please share it with me.
<quiliro>rekado: i did it...i was going to./pre-inst....
<jsierles>`guix pack nss-certs` generates this unusual error: i/o error: /gnu/store/v3badl9wh3zv569zzm3za7gr51dnwgan-profile/etc/ssl/certs/T??B??TAK_UEKAE_K??k_Sertifika_Hizmet_Sa??lay??c??s??_-_S??r??m_3:2.1.17.pem: No such file or directory
<rekado>jsierles: this looks like a locale problem.
<jsierles>the resulting tar exists but without these files.
<quiliro>let me reread your instructions...you said:
<jsierles>rekado: does guix need a special locale setting? running 'tar cf' on the directory directory works fine
<rekado>I don’t know. This looks like a bug to me.
<rekado>looks like setting QT_INSTALL_PREFIX didn’t help
<rekado>we may need to set all of the variables that qscintilla.pro uses
<adfeno>quiliro: Dont worry, everything is going well in the context of learning. Right now, rekado is checking the link he just gave, it seems that qmake is a little more tricky than what we thought. But in the learning side, we are doing fine :)