<robin>that reminds me, i need to get opengenera working on guix (purely for "digital archaeology", i know it's nonfree)
<robin>as you'd expect it has some odd requirements
<robin>(i've mentioned it here before, but unless my reading of the law and license is totally wrong, the US federal government could liberate opengenera tomorrow. i promised to start a petition for that if sanders won, that didn't happen but maybe it's still worth trying)
<robin>i'm pretty sure a petition to get the federal government to do anything not obviously in the interests of capitalists would require a huge number of signatures, and i honestly don't know if enough people care to fill in a form and click a button
<zamfofex>radvendii: I think origins can only be used as sources for packages. (If I remember correctly, the name “origin” was chose instead of “source” to avoid naming conflicts or something similar).
<zamfofex>If you have an origina, you should use it to establish a package first, then use those packages as inputs.
<radvendii>but then how do i keep around that extra argument?
<radvendii>also there's a whole bunch of extra things that get passed in as inputs that i don't want to unpack
<radvendii>fwiw, i found `derivation->output-path` and `origin->derivation` but the former doesn't seem to accept the output of the latter as an argument
<zamfofex>radvendii: You can specify the argument on its own package definition.
<radvendii>how do i get that from the package that has it as an input?
<radvendii>oh. huh. there's a lot of go packages in the guix repo and `guix import go` exists. that's kind of a bummer
<zamfofex>radvendii: How do the dependencies get resolved in Go? If “a” depends on “b” and vice versa, what would you do when bulding either? Do you need to rely on a binary version of the other existing?
<singpolyma>guix import go and go-build-system use GOPATH style builds
<radvendii>zamfofex: there's a lower level of resolution that doesn't allow cyclic dependencies
<radvendii>singpolyma: i'm not sure what that means. sorry, i'm new to go and guix both
<singpolyma>Basically go didn't used to have a module system and everything was based on directory structures that mapped to GitHub urls all in the same one folder
<singpolyma>And and style still works if you set an environment variable to disable modules, which guix currently does
<singpolyma>If I understand correctly you don't really need a cyclic dependency, each just needs the source of the other present at build time, yeah?
<radvendii>yeah, so that's what i'm trying to do. put all the sources in one place
<singpolyma>If you specify the input as just the source of the other package instead of the while package that will break the guile level cycle yeah?
<singpolyma>And then you just need the environment variable set right?
<radvendii>what do you mean "the source of"? like the (origin) field?
<singpolyma>Like there must be an accessory to extract the source/origin of a package
<singpolyma>Hmm, maybe that doesn't work in guile. I'm too spoiled by lazy evaluation. Might have to put the origin in a separate variable and reference it directly
<radvendii>I'm starting to think I can maybe just remove the `build` and `check` phases of everything except the last package and it might just work?
<radvendii>because what i didn't realize is it copies the source into the output
<singpolyma>Oh, sure, that will work if you just want it to build. The binaries aren't used
<radvendii>is it bad form to just neuter all the cyclic inputs? As in, if `A <-> B`, making A' an input to B and B' an import to A
<radvendii>it's not strictly necessary, and makes there be more overall packages floating around
<radvendii>but i think it makes the code slightly cleaner
<radvendii>hmm no wait it doesn't solve my problem never mind
<radvendii>i'm pretty sure the go builder copies all the files (or at least symlinks) rather than setting GOPATH. because if i have two inputs that have the same import path and files (A and A') it complains about permission denied to copy
<brendyn>I git cloned a channel and switched to using file:// to refer to it locally, that way i can update them manually. but with an introduction, i get cannot locate remote tracking brach origin/keyring. any idea how to make that work for a local channel?
<lilyp>civodul As Andrew Tropin observes, that series is not complete, because slurp-file-gexp is missing
<apteryx>seems our pypi importer should transform - into _ again (this is a topic that seems to depend on the phase of the moon -- in the past there was a mixture of them, later it became only '-' on newer servers, now it seems purely '_')
<civodul>vivien: the npm importer is not in Guix proper yet, so you're right and the article is wrong
<civodul>but there are discussions about finally merging it
<apteryx>it's nice that it supports SSH_AUTH_SOCK, but it shouldn't be the only way; perhaps it could consult a file keeping authorized keys also. If that'd suite your use case better, I'd consider implementing such feature to Cuirass if I were you
<Guest53>apteryx The problem is a little deeper. Guile-git is a wrapper around libgit2. And libgit2 doesn't have some of those features
<Guest53>so I don't exactly know where the problem is