<ng0>and then we have to discuss about how multiple libc should be treated in our system. My very basic idea was inherits like the idea i have for libressl, do $name-musl or $name-libressl ... don't know.
<ng0>i should photograph it and kick their behinds if they can't delete it int 3 years, because that's also stated in the optional part. however this state near agency is known for having the worst data protection.
<ng0>lfam: yeah, i tried to compile a new patch addressing the 3rd email. but offloading did not work. so I'll do without offloading now
<lfam>ng0: Which 3rd email? ;) There are many emails
<myglc2>Hi lfam. guix edit started producing 'Couldn't find package location.' with latest git pull && make. Am I missing something?
<lfam>myglc2: Well, I don't use it, so I can't say if it's a regression, but `./pre-inst-env guix edit certbot` gives me Emacs with a dialog telling me that the local variables list in my source tree may not be safe, and then a question about what to do.
<lfam>civodul: For example, there is no concept of releases. Everyone bundles a seemingly arbitrary version control revision. The mechanism for fetching these revisions requires webmasters to include a special <meta> tag on their sites.
<lfam>A filesystem path like '$GOPATH/src/github.com/user/project' is derived from the remote URL, and this path is supposed to uniquely identify the code. But, from my admittedly limited investigation, there is no way to actually uniquely identify the code. No hash or version string or anything like that