This makes me wonder whether maybe we should switch all shell
scripting in Nixpkgs to csh? Wouldn't that solve a lot of problems?
I've heard experts say that csh is generally considered superior
for scripting tasks because of its more intuitive syntax.
I really dislike csh's syntax, and that
Maybe. How much though?
On Thu, Apr 2, 2015 at 9:36 PM, Peter Simons sim...@cryp.to wrote:
Hi Domen,
I'm cancelling staging until nixos-combined catches up and updates the
channel. We have too many other jobset going in the way that have way
lower priority (we had up to 100k builds
Hi Domen,
I'm cancelling staging until nixos-combined catches up and updates the
channel. We have too many other jobset going in the way that have way
lower priority (we had up to 100k builds scheduled few days ago..)
maybe we should increase the number of shares allotted to
Hi Ertugrul,
The last time I tried to switch, Nix started to build everything from
source, including GHC, even with the options described in the Haskell
NG thread.
what architecture do you use? Is it i686-linux by any chance? I'm asking
because Hydra isn't building binaries for that
The last time I tried to switch, Nix started to build everything
from source, including GHC, even with the options described in the
Haskell NG thread.
what architecture do you use? Is it i686-linux by any chance? I'm
asking because Hydra isn't building binaries for that platform at the
If you haven't migrated to Haskell NG yet ... now would be a good time
to do it. (I'm looking at you, Agda.)
I'm currently forced to work on a rather weak machine, so building from
source is prohibitively expensive.
Is there a very short summary of how to do it and still get binary
packages?
Speaking as someone that has been bitten by the non-deterministic package
IDs many times, I'm fully in favor of switching over to GHC 7.10.1 and
removing the old infrastructure. If there's anything I can do to help the
transition, let me know
On Thu, Apr 2, 2015 at 4:51 PM, Peter Simons
Hi Domen,
Maybe. How much though?
right now, nixos:trunk-combined uses 2.24% of the available shares. If
we'd like to dedicate 10% instead, then we'd have to assign 7284 shares.
This should give the job a huge boost, while still leaving a lot of
bandwidth for the rest.
Best regards,
Peter
I've got two computers with nixos, and I can ssh between them without a
password. But if I do a nixos-rebuild with `--option ssh-substitutor-hosts
hostname` they still just download everything from cache.nixos.org. I think
I have the sshServe set up in my configuration.nix:
# nixServeKeys are
http://hydra.nixos.org/jobset/nixpkgs/staging shows 25,000 aborted build
jobs. Is that state intentional in any way? Or can I (or someone else)
restart those builds?
Peter
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
Hello,
I think we should replace the shell and systemd by emacs or a common lisp
implementation.
Kind regards,
Lukas
Am 02.04.2015 um 00:26 schrieb Peter Simons sim...@cryp.to:
Hi guys,
the default builder in Nixpkgs (and pretty much all other shell code in all
our
packages)
I'm cancelling staging until nixos-combined catches up and updates the
channel. We have too many other jobset going in the way that have way lower
priority (we had up to 100k builds scheduled few days ago..)
Once nixos-combined updates the channel, I'll restart staging (hopefully
today?)
Domen
Gettext is currently depending only on libc. Gettext is an input to gcc,
so that's a very important dependency. However gtk 3.16 now requires
gettext to process xml files like glade files, and that requires xml
support via expat.
Gettext is currently compiled so that it finds expat with dlopen,
Hi guys,
I believe that we should switch our default compiler to GHC 7.10.1
within the next three or four weeks -- assuming that no major bug is
discovered in that compiler. It is true that this update will break some
packages, but GHC versions prior to 7.10.x are a disaster for
distributions
14 matches
Mail list logo
