Hi Ludovic,
Lluís Batlle i Rossell virik...@gmail.com skribis:
First, we have to tell hydra to build the branch.
It’s actually being built, but it uses release-small.nix instead of
release.nix.
apparently, you disabled most builds in stdenv-updates with commit 26578. I
agree that
87hb3rw0mo@write-only.cryp.to
e1rau6q-00085y-00.7c6f434c-mail...@smtp23.mail.ru)
Mime-Version: 1.0
Content-type: text/plain; charset=UTF-8
The main point is that the merge should not be rushed.
You are absolutely right. The merge should not be rushed. We don't want
our stdenv to be broken
Hi Peter,
Since stdenv updates are infrequent, we’d rather not do it “just” for
Bash. Instead we usually bundle a list of stdenv package upgrades
(libc, GCC, Coreutils, etc.), hence the branch name. :-)
What about starting looking collectively at what we’d like to have in
the next stdenv
Hi guys,
I would like merge the update to Bash version 4.2 into trunk. Right now,
the changes are in 'stdenv-updates', but that branch contains a whole
lot of changes that I don't know anything about, so I'd rather not be
responsible for merging the entire branch. So my suggestion would be
that I
Is there any reason we can't just do a full merge? I'd rather try to fix any
potentially broken things in updates now than split the current updates into
two stdenv-changing merges.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Peter Simons sim...@cryp.to wrote:
Hi
Hi Shea,
Is there any reason we can't just do a full merge?
who is we?
I, for one, don't want to be responsible for that task. I'll happily
merge those parts of the branch that I know and that I can test, but I
don't want to debug code that I don't use and that I don't know anything
about,
Hi Shea,
Is there any reason we can't just do a full merge?
who is we?
I haven't been around long enough to have been here for the last
stdenv-updates merge, but if I were handling it it would go something like
this:
1. Enable building the full release.nix on stdenv-updates, not just
Hi Shea,
[stdenv-updates merging procedure]
yes, the procedure you described is pretty much how it's going go to.
All interested parties are hereby encouraged to examine the state of the
stdenv-updates branch, and fix all problems that they run into. If in
doubt, please speak up!
Over the
Hi Shea,
[stdenv-updates merging procedure]
yes, the procedure you described is pretty much how it's going go to.
All interested parties are hereby encouraged to examine the state of the
stdenv-updates branch, and fix all problems that they run into. If in
doubt, please speak up!
Over
1. Enable building the full release.nix on stdenv-updates, not just
release-small
Can someone with the right permissions set this up?
pkgs/top-level/release.nix is already correct, it's just not being built
yet, I don't think.
___
nix-dev mailing
10 matches
Mail list logo
