| Commit message (Collapse) | Author | Age |
|\
| |
| | |
_3llo: init at 0.3.0
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The `gemset` field can be an attribute set as well in `buildRubyGem`,
however attribute sets can't be coerced to strings for the environment
set.
The impact should be relatively small as the environment variables are
only used by the `runCommand` script for `bunlderApp` which doesn't
refer to `gemset` at all.
|
| | |
|
|\ \ |
|
| | | |
|
| | | |
|
| |/ |
|
|/ |
|
| |
|
|\
| |
| | |
asciidoctor: include the asciidoctor-epub3 gem
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This has two benefits:
- Anyone else using the `mathematical` gem will benefit from the config.
- The gem config overrides the default one, so we were losing the fixes
for other gems.
I had to change how the update script works. Now it looks at the `gems`
passthru from `bundlerApp`.
|
|/ |
|
|
|
|
|
|
| |
* treewide: remove unused variables
* making ofborg happy
|
|
|
|
|
|
|
| |
The manual documents both bundlerEnv and bundlerApp as providing `env`
and `wrappedRuby` attributes on the resulting derivations. However only
bundlerEnv actually had these attributes. Update bundlerApp to provide
the same passthru that bundlerEnv does.
|
| |
|
| |
|
|\
| |
| | |
bundlerApp: don't execute postBuild twice
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
|\
| |
| | |
cocoapods-beta: init at 1.7.0.beta.3
|
| |
| |
| |
| |
| | |
Like `bundlerEnv`, the `gemdir` parameter to `bundlerApp` can be omitted
if all 3 of `gemfile`, `lockfile`, and `gemset` are provided.
|
|/ |
|
|\
| |
| | |
ruby-modules/gem: fix path to git checkout
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In case of the gem type 'git', nix-bundle-install.rb was called with
wrong path to the git checkout.
${src} does contain the sources, but not the newly generated .git dir,
which is created in the buildPhase of pkgs/development/ruby-modules/gem/default.nix
In some rare cases, this .git dir is needed at installPhase.
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Changing leaveDotGit to git chacha on build
* Removing debugging cruft
* Simpler git handling
* Can't clobber index after `add`
* Update pkgs/development/ruby-modules/gem/default.nix
Useful comments
Co-Authored-By: nyarly <nyarly@users.noreply.github.com>
* Update pkgs/development/ruby-modules/gem/default.nix
Comments are useful
Co-Authored-By: nyarly <nyarly@users.noreply.github.com>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes https://github.com/manveru/bundix/issues/42.
|
|
|
| |
Note: on macOS, it works without this config. Testing on Ubuntu/Debian with the parent sha will produce an error about extconf.rb failing to find openssl/sha.h.
|
|
|
|
|
|
|
|
|
|
|
| |
`digest-sha3` is a C-extension gem which fails to build on Nix because
it uses non-literals as format strings which is forbidden by the default
Nix hardening settings. There is a pull request to fix that ([1]), but
the gem seems to be abandoned.
This PR disables the "format" hardening for `digest-sha3`.
[1]: https://github.com/phusion/digest-sha3-ruby/pull/8
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With the v6.0.0 release of the `rbnacl` gem, it does not longer depends
on `rbnacl-libsodium` gem (which is now deprecated ([1])) to package the
`libsodium` library and should use the one provided by the distribution;
it raises an error if `rbnacl-libsodium` is detected ([2]).
Unfortunately, default gem config patches `rbnacl` unconditionally ([3]),
which means that newer versions of `rbnacl` fail at startup.
[1]: https://github.com/crypto-rb/rbnacl-libsodium/issues/29
[2]: https://github.com/crypto-rb/rbnacl/blob/c176fc0bd8be74cf62c93a4b122e220ce4895348/lib/rbnacl.rb#L4-L8
[3]: https://github.com/NixOS/nixpkgs/blob/9fd099a6ae1690909ebf40145e4cdabd67179676/pkgs/development/ruby-modules/gem-config/default.nix#L300-L306
|
|\
| |
| | |
Make myself a Ruby maintainer
|
| | |
|
|\ \
| |/
|/| |
bundler: 1.17.1 -> 1.17.2
|
| | |
|
|\ \
| | |
| | | |
vagrant: build and install vagrant-libvirt plugin
|
| |/
| |
| |
| |
| | |
Based on 1d9798c8591bbbed6e6b9ca5c1811ff507b88b9a and
90a804c50af327077e7a219a425e8536bb097e39
|
|/
|
|
| |
This removes the patch for support of Dell X-series because
oxidized now includes a model for these switches.
|
|
|
|
|
|
|
| |
"default" isn't really a group, it's more the absence of one. With
Bundler, this means that a gem should be installed unconditionally,
regardless of which groups are specified. It doesn't really make sense
to allow these gems to be omitted from a bundlerEnv.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This wasn't really an issue until the latest minor release of Bundix
(2.4), because prior to then Bundix didn't emit group attributes, and so
this functionality of bundlerEnv wasn't really used. However, it is now
apparent that a better default for bundlerEnv would be to include all
gem groups by default, not just the default group. This matches the
behavior of Bundler, and makes more sense, because the default group
alone isn't necessarily useful for anything -- consider a Rails app with
production, development, and test groups. It has the additional benefit
of being backwards compatible with how this would have worked before the
Bundix update.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Suppose I have a Gemfile like this:
source "https://rubygems.org"
gem "actioncable"
gem "websocket-driver", group: :test
The gemset.nix generated by Bundix 2.4.1 will set ActionCable's groups
to [ "default" ], and websocket-driver's to [ "test" ]. This means that
the generated bundlerEnv wouldn't include websocket-driver unless the
test group was included, even though it's required by the default group.
This is arguably a bug in Bundix (websocket-driver's groups should
probably be [ "default" "test" ] or just [ "default" ]), but there's no
reason bundlerEnv should omit dependencies even given such an input --
it won't necessarily come from Bundix, and it would be good for
bundlerEnv to do the right thing.
To fix this, filterGemset is now a recursive function, that adds
dependencies of gems in the group to the filtered gemset until it
stabilises on the gems that match the required groups, and all of their
recursive dependencies.
|