People
 :bowtie: |
😄 :smile: |
😆 :laughing: |
|---|---|---|
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
😗 :kissing: |
😙 :kissing_smiling_eyes: |
😛 :stuck_out_tongue: |
There a times when you need to build something from the nix unstable channel. For example the master contains a new package you need, but the next nixpkgs release is somewhere in the future, and you need this package now. In this guide I want to show how to install packages from unstable by using nix-env. Furthermore I hope to give a basic understanding of the channels concept.
A channel is a set of expressions which includes severall build, installation and configuration instructions for packages, services and the system itself. The repository normaly used here is nixpkgs. It is developed at https://github.com/NixOS/nixpkgs.
The unstable channel is a copy of the NixOS/nixpkgs master. It is pulled from github once in a while and will be available from a mirror under https://nixos.org/channels/nixpkgs-unstable. Since NixOS uses half-anual released stable channels, some changes (especially new f
| import re | |
| import json | |
| from email.message import EmailMessage | |
| from email import message_from_string | |
| class InvalidMetadata(Exception): | |
| pass | |
| SINGLE_USE = [ | |
| "Metadata-Version", |
| #include <iostream> | |
| #include <cstring> | |
| #include <type_traits> | |
| #include <utility> | |
| #include <tuple> | |
| // graph descriptions | |
| template <int... Next> | |
| using AdjacentList = std::integer_sequence<int, Next...>; |
| #include <type_traits> | |
| template <class From, class To> | |
| concept is_convertible = requires(From f){ | |
| { static_cast<To>(f) } -> To; | |
| }; | |
| template <typename Fst> | |
| concept BaseFst = requires { |
| #include <iostream> | |
| #include <complex> | |
| #include <cmath> | |
| #include <utility> | |
| #include <chrono> | |
| #include <array> | |
| // std::complex<T>::operators -- not constexpr in C++17 | |
| template <class T> |
This document contains some ideas for additions to the Nix language.
The Nix package manager, Nixpkgs and NixOS currently have several problems:
enableFoo, but there is no way for the Nix
UI to discover them, let alone to provide programmatic ways to
How do you send information between clients and servers? What format should that information be in? What happens when the server changes the format, but the client has not been updated yet? What happens when the server changes the format, but the database cannot be updated?
These are difficult questions. It is not just about picking a format, but rather picking a format that can evolve as your application evolves.
By now there are many approaches to communicating between client and server. These approaches tend to be known within specific companies and language communities, but the techniques do not cross borders. I will outline JSON, ProtoBuf, and GraphQL here so we can learn from them all.