Hi, not to rain on the parade, but
> - All data lives in IPFS: no local filesystem, no Guix store.
> A personal computing device only stores references to information
> that its owner cares about.
>
> - All computations are equal: no distinction between "software builds"
> and ever
‐‐‐ Original Message ‐‐‐
On Wednesday, May 22, 2019 8:22 PM, Amin Bandali wrote:
> That’s a typo; it should have been https://audio-video.gnu.org.
There is also no https://audio-video.gnu.org/guix/
I presume that has indeed not been set up yet?
I also tried it without the trailing slash.
‐‐‐ Original Message ‐‐‐
On Wednesday, May 22, 2019 7:06 PM, Laura Lazzati
wrote:
> Hi Guix!
>
> I have created the site: https://archive.org/details/guix-videos
> where I will be pushing the documentation videos that I created
> during my internship and that Paul helped a a lot sharing
The upek folder in the source I downloaded seems to contain compiled shared
libraries in the lib and lib64 subfolders, so that's a bad sign.
‐‐‐ Original Message ‐‐‐
On Friday, May 17, 2019 1:52 PM, Raghav Gururajan wrote:
> Hello Guix!
>
> I came across this Fingerprint GUI applicatio
Hi, I'm (still) trying to build Mininet and it uses both a Makefile for
building an C executable and setup.py to install its Python modules. I looked
at the soundconverter package to get some hints for mixing build systems but
couldn't get very far, I get all sorts of (mostly cryptic) error mess
Not a microkernel, but Plan 9's file system semantics might be worth playing
around with. The POSIX emulation probably wouldn't be able to support a
full-blown Guix system, but the OS is very well worth taking hints from, at the
very least. Overlays would imho be much nicer to work with than pat
Not directly connected, but have yall seen how rust packages its documentation?
Personally I am REALLY not a fan of everything running in a separate browser,
one browser is more than enough. But as long as there is one browser, why not
generate a searchable index that uses JS the way Rust did it
