Commit Graph

113 Commits

Author SHA1 Message Date
zimbatm
2f791c7444 terraform: 0.6.16 -> 0.7.0 2016-08-03 09:53:20 +01:00
Kamil Chmielewski
81efd0c82d mesos: FIX Failed to extract tgz 2016-07-27 10:11:33 +02:00
Frederik Rietdijk
7d69e5dda2 Merge pull request from siddharthist/terraform/0.6.15->0.6.16
terraform: 0.6.15 -> 0.6.16
2016-07-15 11:19:28 +02:00
rushmorem
3b27257e9a habitat: fix naming collision 2016-07-14 05:40:09 +02:00
rushmorem
ea15a54ef2 habitat: add an option to run in an FHS chroot
`hab studio enter` as well as other `hab` commands that make use
of the studio assume an FHS system when creating a chroot.

See https://github.com/habitat-sh/habitat/issues/994
2016-07-14 04:36:58 +02:00
Langston Barrett
f3262a209b terraform: 0.6.15 -> 0.6.16 2016-07-13 18:32:13 +02:00
rushmorem
0604af9212 nomad: 0.3.2 -> 0.4.0 2016-06-30 20:30:22 +02:00
rushmorem
531cdf4be1 habitat: build from source 2016-06-27 13:38:10 +02:00
rushmorem
5f2dc4bc05 habitat: init at 0.7.0 2016-06-25 21:44:54 +02:00
Bjørn Forsman
bd01fad0ed Captialize meta.description of all packages
In line with the Nixpkgs manual.

A mechanical change, done with this command:

  find pkgs -name "*.nix" | \
      while read f; do \
          sed -e 's/description\s*=\s*"\([a-z]\)/description = "\u\1/' -i "$f"; \
      done

I manually skipped some:

* Descriptions starting with an abbreviation, a user name or package name
* Frequently generated expressions (haskell-packages.nix)
2016-06-20 13:55:52 +02:00
Kamil Chmielewski
1dfae0678d nomad: extracted from goPackages 2016-06-09 13:08:10 +02:00
Kamil Chmielewski
8cd1d4cda5 buildGoPackage: use Go 1.6 by default 2016-06-09 13:08:10 +02:00
Kamil Chmielewski
734d152977 buildGo16Packages: fetchgit -> fetchFromGitHub 2016-06-09 13:08:10 +02:00
Kamil Chmielewski
7eb671ebcd no more goPackages 2016-06-09 13:08:00 +02:00
Kamil Chmielewski
e89a086f06 terraform: extracted from goPackages 2016-06-09 11:22:02 +02:00
rushmorem
21c83f294d kubernetes: v1.0.3 -> v1.2.4 2016-06-06 19:25:32 +02:00
Tuomas Tynkkynen
bac26e08db Fix lots of fetchgit hashes (fallout from ) 2016-06-03 17:17:08 +03:00
Tuomas Tynkkynen
05d8174b0e treewide: Make explicit that 'dev' output of subversion is used 2016-05-19 10:04:37 +02:00
Tuomas Tynkkynen
2a73de6e6c treewide: Make explicit that 'dev' output of openssl is used 2016-05-19 10:02:23 +02:00
Tuomas Tynkkynen
603dcd6263 treewide: Make explicit that 'dev' output of libnl is used 2016-05-19 10:00:43 +02:00
Tuomas Tynkkynen
674eb400ef treewide: Make explicit that 'dev' output of libevent is used 2016-05-19 10:00:40 +02:00
Tuomas Tynkkynen
29694b43b6 treewide: Make explicit that 'dev' output of apr is used 2016-05-19 10:00:24 +02:00
Peter Simons
8e462995ba Bring my stdenv.lib.maintainers user name in line with my github nick. 2016-05-16 22:49:55 +02:00
Charles Strahan
f8f16b1a36 mesos: 0.27.1 -> 0.28.0 2016-03-31 04:17:19 -04:00
Kevin Cox
8b7adf808e mesos: Patch more executable paths. 2016-03-11 09:23:48 -05:00
Robin Gloster
937574a206 Merge pull request from zimbatm/remove-rq
rq: package removed
2016-03-09 08:22:17 +01:00
zimbatm
0ced8f386c rq: package removed
rq only compiles with ruby 1.8 which we don't distribute anymore.

the source is dead.

there is a 1.9 branch over https://github.com/pjotrp/rq that hasn't been
touched for 4 years.
2016-03-08 21:36:59 +00:00
Mathieu Boespflug
6cf1853f29 spark: Fix tarball hash.
Maybe tarball changed upstream. Who knows.

Fixes 
2016-03-07 23:16:26 +01:00
joachifm
dca363b9a0 Merge pull request from kevincox/mesos-0.27.1
Mesos: 26.0 -> 27.1
2016-03-06 14:44:26 +00:00
Kevin Cox
ee9b151f5b marathon: 0.15.1 -> 0.15.3 2016-03-06 08:05:26 -05:00
Kevin Cox
2843d83905 Mesos: 26.0 -> 27.1 2016-03-05 22:49:48 -05:00
Bruno Bzeznik Bruno.Bzeznik@imag.fr
15c4167d28 kanif: init at 1.2.2 2016-03-04 12:22:29 +01:00
Lancelot SIX
95f22a6fb5 pkgs.taktuk: fix remote url 2016-03-04 10:30:42 +01:00
Lancelot SIX
f689bc9629 Merge pull request from bzizou/taktuk
taktuk: init at 3.7.5
2016-03-04 10:27:19 +01:00
Bruno Bzeznik Bruno.Bzeznik@imag.fr
92e86f03b0 taktuk: init at 3.7.5 2016-03-04 10:11:08 +01:00
Mathieu Boespflug
936312879c spark: 1.4 -> 1.6. 2016-02-18 18:29:44 +01:00
Vladimír Čunát
e9520e81b3 Merge branch 'master' into staging 2016-02-17 10:06:31 +01:00
Samuel Rivas
d72fad9ee4 spark: export the assembly to /share/java, fixes
So that we can compile applications that depend on spark
2016-02-15 21:26:03 +01:00
Samuel Rivas
704e923ad5 spark: reduce default shell log verbosity 2016-02-15 21:26:03 +01:00
Samuel Rivas
d213089a25 spark: 1.4.0 -> 1.5.2 2016-02-15 21:26:03 +01:00
Pascal Wittmann
b9db5a9574 Merge pull request from kamilchm/marathon
marathon: 0.14.1 -> 0.15.1
2016-02-15 15:05:11 +01:00
Kevin Cox
d5ed1637b6 mesos: 0.23.0 -> 0.26.0
Update mesos to 0.26.0 and build with SSL support.
2016-02-14 08:22:47 -05:00
Kamil Chmielewski
55b7f03e3b marathon: 0.14.1 -> 0.15.1 2016-02-09 11:45:06 +01:00
Vladimír Čunát
a115bff08c Merge branch 'master' into staging 2016-02-07 13:52:42 +01:00
Guillaume Maudoux
9f358f809d Configure a default trust store for openssl 2016-02-03 12:42:01 +01:00
Kamil Chmielewski
40eaffdc1b marathon: 0.8.1 -> 0.14.1 2016-01-29 18:31:13 +01:00
Vladimír Čunát
7c879d342d Merge : improve FreeBSD support 2016-01-05 09:50:10 +01:00
Charles Strahan
b6c06e216b ruby: new bundler infrastructure
This improves our Bundler integration (i.e. `bundlerEnv`).

Before describing the implementation differences, I'd like to point a
breaking change: buildRubyGem now expects `gemName` and `version` as
arguments, rather than a `name` attribute in the form of
"<gem-name>-<version>".

Now for the differences in implementation.

The previous implementation installed all gems at once in a single
derivation. This was made possible by using a set of monkey-patches to
prevent Bundler from downloading gems impurely, and to help Bundler
find and activate all required gems prior to installation. This had
several downsides:

* The patches were really hard to understand, and required subtle
  interaction with the rest of the build environment.
* A single install failure would cause the entire derivation to fail.

The new implementation takes a different approach: we install gems into
separate derivations, and then present Bundler with a symlink forest
thereof. This has a couple benefits over the existing approach:

* Fewer patches are required, with less interplay with the rest of the
  build environment.
* Changes to one gem no longer cause a rebuild of the entire dependency
  graph.
* Builds take 20% less time (using gitlab as a reference).

It's unfortunate that we still have to muck with Bundler's internals,
though it's unavoidable with the way that Bundler is currently designed.
There are a number improvements that could be made in Bundler that would
simplify our packaging story:

* Bundler requires all installed gems reside within the same prefix
  (GEM_HOME), unlike RubyGems which allows for multiple prefixes to
  be specified through GEM_PATH. It would be ideal if Bundler allowed
  for packages to be installed and sourced from multiple prefixes.
* Bundler installs git sources very differently from how RubyGems
  installs gem packages, and, unlike RubyGems, it doesn't provide a
  public interface (CLI or programmatic) to guide the installation of a
  single gem. We are presented with the options of either
  reimplementing a considerable portion Bundler, or patch and use parts
  of its internals; I choose the latter. Ideally, there would be a way
  to install gems from git sources in a manner similar to how we drive
  `gem` to install gem packages.
* When a bundled program is executed (via `bundle exec` or a
  binstub that does `require 'bundler/setup'`), the setup process reads
  the Gemfile.lock, activates the dependencies, re-serializes the lock
  file it read earlier, and then attempts to overwrite the Gemfile.lock
  if the contents aren't bit-identical. I think the reasoning is that
  by merely running an application with a newer version of Bundler, you'll
  automatically keep the Gemfile.lock up-to-date with any changes in the
  format. Unfortunately, that doesn't play well with any form of
  packaging, because bundler will immediately cause the application to
  abort when it attempts to write to the read-only Gemfile.lock in the
  store. We work around this by normalizing the Gemfile.lock with the
  version of Bundler that we'll use at runtime before we copy it into
  the store. This feels fragile, but it's the best we can do without
  changes upstream, or resorting to more delicate hacks.

With all of the challenges in using Bundler, one might wonder why we
can't just cut Bundler out of the picture and use RubyGems. After all,
Nix provides most of the isolation that Bundler is used for anyway.

The problem, however, is that almost every Rails application calls
`Bundler::require` at startup (by way of the default project templates).
Because bundler will then, by default, `require` each gem listed in the
Gemfile, Rails applications are almost always written such that none of
the source files explicitly require their dependencies. That leaves us
with two options: support and use Bundler, or maintain massive patches
for every Rails application that we package.

Closes 
2015-12-29 09:30:21 -05:00
Domen Kožar
4e4931507b fix mesos build, fixes 2015-12-28 22:28:38 +01:00
Domen Kožar
d83a97823c buildPythonPackage: fix a few more wheel packages 2015-11-21 21:44:12 +01:00