Hi Bjørn,
I have read that thread. I agree with you 100% that native builds (on real
or virtual hardware) is the only way this can work. Upstream doesn't
usually care if their software can cross compile, and they can't maintain
it themselves even if they did. Sometimes it isn't even an option, e.g
On 28 January 2015 at 02:49, Luke Clifton wrote:
...
> My plan, should I ever get the time, is to set up a virtual machine, try and
> bootstrap NixOS for ARM in that, set up hydra, build nixpkgs and then serve
> the results to my embedded platforms. I also have dreams of creating
> firmware images
I cannot run the 'trivial.nix' example from
http://hydra.nixos.org/build/18990240/download/1/manual/manual.html#idm140737319352096
"Deploying a VirtualBox VM" on MacOS Yosemite 10.10.
The VM starts (I see a login screen), but the build process quits with
---8<---
building path(s)
‘/nix/sto
Hi Peter,
Have you looked into how we could make haskell closures smaller with multiple
outputs? At the very least separating ghc’s shared libs from the compiler
should be a big win, but ideally we would also separate bin and lib for haskell
packages as well.
~Shea
Hi James,
I too am interested in getting NixOS running on ARM, but unfortunately I am
currently unable to dedicate time to the project.
My problem has always been lack of RAM in my ARM devices. I work mostly
with embedded Linux platforms where RAM is < 256MB. To provide perspective,
my Laptop (co
Hi,
I forgot to say, that was my first email to the list. So hi
everyone! I was told about NixOS by Doaitse Swierstra at Summer School
Utrecht 2013 on the Applied Functional Programming course. I went to
FOSDEM for the first time last year, seeing Domen's excellent talk, and
I've been in Freeno
Hi all,
I presume that if you're going to FOSDEM this year you're already aware,
but just in case I'd like to remind you that NixOS will have a table at
FOSDEM and it would be awesome if you could volunteer to man it and answer
questions about NixOS etc.
More explanation at https://nixos.org/wiki
I am writing a nix expression to port some libraries from another distro.
The libraries have slightly non-standard locations so I would typically add
some line to my .bashrc file like
export SOMEVAR="somestring"
export SOMEPATH=/opt/path/to/libs
export LD_LIBRARY_PATH=$SOMEPATH:$LD_LIBRARY_PATH.
Em 26/01/2015 04:37, "Marc Weber" escreveu:
>
> It got implemented somewhen in the past, some people told about
> bash completion being annoying in some cases (-> [1]) .. which means the
perfect
> solutions means conditional opt-in/out eventually.
>
> bash.nix has:
>
> interactiveShellInit =
So what about `config.environment.etc."hosts.allow"`? Make the interface be
`config.environment.etc = { path:"hosts.allow"; ...;};`?
On Tue Jan 27 2015 at 5:02:27 PM Eelco Dolstra
wrote:
> Hi,
>
> On 27/01/15 16:58, Wout Mertens wrote:
>
> > Nix could be extended to accept `rec { "foo.bar" = "te
https://github.com/dmgerman/ninka is not really an easy solution... Perhaps
an enterprising individual could integrate it with Nix so that it will
propose licenses where missing and complains where licenses aren't correct
(with warning squelch flag in the meta once an unclear license was
identified
Nix could be extended to accept `rec { "foo.bar" = "test"; bar =
${"foo.bar"};}'?
Is this an important use case?
On Mon Jan 26 2015 at 12:58:25 PM Eelco Dolstra
wrote:
> Hi,
>
> On 26/01/15 10:55, Peter Simons wrote:
>
> > consider the following recursive attribute set:
> >
> > rec
> > {
Hi,
On 27/01/15 16:58, Wout Mertens wrote:
> Nix could be extended to accept `rec { "foo.bar" = "test"; bar =
> ${"foo.bar"};}'?
Well, it was probably a mistake to allow string syntax for variable names in the
first place. It might be better to allow '.' to be escaped in variables names:
rec {
Kirill Elagin writes:
> `man default.pa` has to say:
>
>> The PulseAudio sound server interprets the file
>> ~/.config/pulse/default.pa on startup, and when that file doesn't
>> exist /etc/pulse/default.pa.
I'm embarrassed to admit that through a long series of coincidences and
assumptions this t
Hi,
On 27/01/15 10:16, Anderson Torres wrote:
> I am Anderson Torres, a "wannabe" Computer Scientist (I am studying to
> admissional exams for a Brazilian CS undergrad course), and there is
> about one year I am a NixOS user.
>
> I want to port/package Trinity for NixOS, because I really liked t
Hi,
On 27/01/15 12:53, Wout Mertens wrote:
> See http://hydra.nixos.org/jobset/nixpkgs/staging#tabs-evaluations
>
> There's 4 evaluations with queued jobs, why don't they get cancelled when the
> next evaluation happens?
Because Hydra doesn't cancel jobs automatically.
I've cancelled them manu
On Tue, Jan 27, 2015 at 11:57 AM, Michael Raskin <7c6f4...@mail.ru> wrote:
>>> From what I understand, there's no way to use `startx' with systemd.
>>
>>There might be some NixOS-specific issues here, I’m not sure. But in
>>general there _is_ a way: you just login on the text console and run
>>`sta
See http://hydra.nixos.org/jobset/nixpkgs/staging#tabs-evaluations
There's 4 evaluations with queued jobs, why don't they get cancelled when
the next evaluation happens?
Just trying to understand how hydra works...
Wout.
___
nix-dev mailing list
nix-de
Anderson Torres writes:
> Hello, Nixers and Trinity users!
>
> I am Anderson Torres, a "wannabe" Computer Scientist (I am studying to
> admissional exams for a Brazilian CS undergrad course), and there is
> about one year I am a NixOS user.
>
> I want to port/package Trinity for NixOS, because I
Hello, Nixers and Trinity users!
I am Anderson Torres, a "wannabe" Computer Scientist (I am studying to
admissional exams for a Brazilian CS undergrad course), and there is
about one year I am a NixOS user.
I want to port/package Trinity for NixOS, because I really liked the
old KDE3.x series! I
On Mon, Jan 26, 2015 at 6:46 PM, Peter Jones wrote:
> From what I understand, there's no way to use `startx' with systemd.
There might be some NixOS-specific issues here, I’m not sure. But in
general there _is_ a way: you just login on the text console and run
`startx`.
> That's my preference, b
`man default.pa` has to say:
> The PulseAudio sound server interprets the file
> ~/.config/pulse/default.pa on startup, and when that file doesn't exist
> /etc/pulse/default.pa.
Just out of curiosity I checked the source and it seems that this line
was already there in 2007 and the code tha
22 matches
Mail list logo