Unlike most distros, the NixOS download page doesn't appear to have
GPG signatures for the CD images.
https://nixos.org/nixos/download.html
vs.
https://www.debian.org/CD/verify
http://distfiles.gentoo.org/releases/amd64/autobuilds/20160218/install-amd64-minimal-20160218.iso.DIGESTS.asc
In fact,
> On Tue, 23 Feb 2016 at 21:29 Vladimír Čunát wrote:
> > My personal opinion is that this is mostly an excuse. It's a XML subset
> > and everyone should know at least a bit of (X)HTML or similar stuff.
> > Note that for almost all docs we use ~10 types of tags and the format is
Basically wrote the doc in markdown and then:
```
$ nix-env -iA nixos.pandoc
$ pandoc -f markdown -t docbook release.md > release.xml
```
The output file wasn't exactly right, I had to replace `` to `` tags and wrap it in a tag. That
was quickly done and less work that writing in docbook
On Thu, Feb 25, 2016 at 2:00 PM, Eelco Dolstra
wrote:
> Hi,
>
> On 24/02/16 01:14, Anderson Torres wrote:
>
> > 2016-02-23 19:22 GMT-03:00 zimbatm :
> >> I started writing some docbook. Maybe I will get used to it but writing
> >> `foobar` is way
Hi,
On 24/02/16 01:14, Anderson Torres wrote:
> 2016-02-23 19:22 GMT-03:00 zimbatm :
>> I started writing some docbook. Maybe I will get used to it but writing
>> `foobar` is way more painful
>> that `* foobar` in markdown. Especially in writing I think it's important to
>>
Nobody has written the Nix/NixOS book yet.
On 24/02/2016 11:14 AM, "Anderson Torres"
wrote:
> 2016-02-23 19:22 GMT-03:00 zimbatm :
> > I started writing some docbook. Maybe I will get used to it but writing
> > `foobar` is way more
> painful
> >
Hi everyone,
I'm trying to debug
https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/compilers/ghcjs/default.nix
,
which is a callPackage-style Nix function that expects lots of arguments.
Is there a quick way to get a nix-shell or other type of debugging
environment for such a package?