Re: [Nix-dev] Preference for building from source

As far as the particular examples of Eclipse and Gradle, I think the issue is that building java packages (especially big complicated ones like those) is currently rather painful in Nix. Unlike many other language ecosystems, we don't have a wealth of prepackaged libraries and dependencies for the

Re: [Nix-dev] Preference for building from source

Hi, On 08/01/16 11:26, Rok Garbas wrote: > Building from source is always possible. That's what Hydra.nixos.org > > does for you. The binaries from there are used iff the build > instructions are exactly the same as what is available already. > > > I thi

Re: [Nix-dev] Preference for building from source

On 01/08/2016 11:26 AM, Rok Garbas wrote: > I think Juho (awesome name by the way!) was trying to figure out what > the is the general policy of nixpkgs expressions. Oh, I see now I got the meaning wrong. Good summary, Rok! --Vladimir smime.p7s Description: S/MIME Cryptographic Signature

Re: [Nix-dev] Preference for building from source

On Fri, Jan 8, 2016 at 11:16 AM, Vladimír Čunát wrote: > On 01/08/2016 11:06 AM, Juho Östman wrote: > > As for me, I think packages should be built from source whenever it is > possible. > > Building from source is always possible. That's what Hydra.nixos.org > does for you. The binaries from the

Re: [Nix-dev] Preference for building from source

On 01/08/2016 11:06 AM, Juho Östman wrote: > As for me, I think packages should be built from source whenever it is > possible. Building from source is always possible. That's what Hydra.nixos.org does for you. The binaries from there are used iff the build instructions are exactly the same as wh

[Nix-dev] Preference for building from source

Does nixpkgs have a policy on building packages preferably from source? I have noticed the nix scripts of a few packages fetch a binary package instead of building from source, even though a source should also be available, for example Eclipse and Gradle. Is this a conscious decision, or were these