Just to add to this, something I haven't seen neatly documented but I
personally find very helpful (if a bit rough) is to run "genericBuild"
from within nix-shell, which will run the phases from the
derivation... and usually fail to install during installPhase. I
often start this and then just
On Tue, Mar 21, 2017 at 10:01 AM, Kosyrev Serge wrote:
>
> Dmitry Kalinkin writes:
>> On 17 Mar 2017, at 17:44, Vladimír Čunát wrote:
>>
>> I do believe the intention was for "SW distribution" etc, at least
>> primarily, and the suitability for
Dmitry Kalinkin writes:
> On 17 Mar 2017, at 17:44, Vladimír Čunát wrote:
>
> I do believe the intention was for "SW distribution" etc, at least
> primarily, and the suitability for development is a by-product due to
> some properties, e.g. easy (non-)mixing of development
Another option is to add a powerful remote builder on the local network. It
doesn't beat incremental rebuilds but helps with having the laptop taking
off and trying to burn my legs. Old desktop machines from ebay are not too
expensive and still beat the laptop capacity.
On Sat, 18 Mar 2017 at
A while ago I wrote a wrapper around nix-shell that helps with running
the build steps in correct manner and order (among with other niceties
like automatically creating a temporary build directory and making
$out point to a path in /tmp/):
https://github.com/dezgeg/nix-debug-shell
I mainly wrote
nix-shell on its installPhase has no rights to write to /nix/store,
installPhase always fails.
I am thinking about something like converting a derivation (a .drv
file) into two files:
1. a .sh file, which would do unpackPhase, patchPhase, configurePhase,
buildPhase using the current directory,
On 17-03-17 05:34pm, Dmitry Kalinkin wrote:
> Also it is funny how your statement is followed by some good advice on how to
> turn nix into even better dev platform. I will only add that one could also
> use ccache to speedup builds:
>
> my_cool_package.override { stdenv = pkgs.ccacheStdenv; }
What I meant in the original question is more about troubleshooting
than development.
That development is incorporated in the deployment chain all other
steps are already powered by nix: build a (patched) kernel, then build
system closures with it, then test-driver scripts, then deploy/run
them...
On 03/17/2017 07:04 PM, Volth wrote:
> "nix-shell" would be a super option here if it could handle
> "installPhase"
For my paid work (upstream) I'm perfectly comfortable with nix-shell on
an expression that is slightly modified from the nixpkgs version. I
solve the installing just by specifying
Nix is 'software distribution platform', not a dev platform.
Depending on the task other solutions might be better.
For instance restarting nginx/ apache the nixos way is also slower than
edit/restart cycle on 'debian'. So use the right tool / env for your
job.
There was a hack to impurely
On 17/03/17 16:00, Volth wrote:
> What could be done here?
nix-shell, and the upstream recommended build procedure.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
11 matches
Mail list logo