about summary refs log tree commit diff
path: root/pkgs/tools/audio
Commit message (Collapse)AuthorAge
* beets: add missing dependency six, fixes #20946Frederik Rietdijk2016-12-06
|
* beets: Set Python version via top-level attributeaszlig2016-12-03
| | | | | | | | | | | | | | | | | | | | | | | This largely reverts commit 599312739e3a338f923e6c22ab183178ca49c7b6. The main reason is that it breaks the plugins, because the mentioned commit didn't change the attributes for the plugins as well. But instead of just fixing the attributes when we import the plugin packages, let's just override pythonPackages in all-packages.nix. Right now, Beets is in transition to Python 3, so we don't need to wait that long until we can remove the dependency on Python 2: https://github.com/beetbox/beets/releases/tag/v1.4.1 Once Python 3 support is no longer beta, we can just change this by changing one line only instead of several. Tested this by building beets with both external plugins. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @FRidh
* Merge remote-tracking branch 'upstream/staging' into masterTuomas Tynkkynen2016-11-30
|\
| * beets: use python2Frederik Rietdijk2016-11-24
| |
* | beets: 1.3.19 -> 1.4.1aszlig2016-11-28
|/ | | | | | | | | | | | | | | | | | Full upstream release announcement: https://github.com/beetbox/beets/releases/tag/v1.4.1 I had to rebase the keyfinder-default-bin.patch in order to apply with the new release. Other than that I didn't test whether beets works on my machine, as I have a more or less temporary setup at the moment. However, since the bump of mutagen to version 1.34 in commit 555928c228634b4c372f38e6ea5c320c1662711b, the mediafile tests fail and thus this commit unbreaks beets. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* darkice: fix and simplify dependenciesFranz Pletz2016-10-31
|
* Merge remote-tracking branch 'upstream/master' into HEADFrederik Rietdijk2016-10-26
|\
| * qastools: 0.18.1 -> 0.21.0Alexander V. Nikolaev2016-10-24
| |
* | Python: remove modules and pythonFullFrederik Rietdijk2016-10-10
|/
* bash-completion: change attribute nameRobert Helgesson2016-09-28
| | | | | | This changes the attribute name of bash-completion from `bashCompletion` to `bash-completion`. Keeps `bashCompletion` as an alias for the new name.
* beets: Use pythonPackages.buildPythonApplicationaszlig2016-09-27
| | | | | | | | | | | | | | | | | The top-level attribute has been removed in commit 771ed59b48bc1257439b4529426cc9047aebc27b. This has been partially resolved in commit 18bdd44729a4e3d58220ed4789a91aabd20470dd. The latter change however only addressed the main derivations but missed out on the plugins. This is now done by just passing pythonPackages down the chain. Tested by only evaluating the expression, not building. Signed-off-by: aszlig <aszlig@redmoonstudios.org> Cc: @domenkozar, @pjones, @profpatsch
* beets: pass in pythonPackagesFrederik Rietdijk2016-09-26
|
* pnmixer: 2016-04-23 -> 0.7José Romildo Malaquias2016-09-19
|
* Merge commit 'refs/pull/18498/head' of git://github.com/NixOS/nixpkgsNikolay Amiantov2016-09-13
|\
| * treewide: explicitly specify gtk and related package versionsKirill Boltaev2016-09-12
| |
* | beets: fix keyfinder plugin by addind keyfinder-cli dependencyMichal Rus2016-09-10
| |
* | beets: add copyartifacts pluginMichal Rus2016-09-10
|/
* darkice: 1.2 -> 1.3Franz Pletz2016-08-23
|
* Remove top-level dbus_python and pythonDBus.Frederik Rietdijk2016-08-16
| | | | | | | | | See #11567. Furthermore, it renames pythonPackages.dbus to pythonPackages.dbus- python as that's the name upstream uses. There is a small rebuild but I couldn't figure out the actual cause.
* treewide: Add lots of meta.platformsTuomas Tynkkynen2016-08-02
| | | | Build-tested on x86_64 Linux & Mac.
* treewide: Fix meta.platforms related typosTuomas Tynkkynen2016-08-02
|
* beets: 1.3.17 -> 1.3.19Bjørn Forsman2016-08-02
| | | | | | | The echonest plugin was removed in 3.18 because the API it used is shutting down. You might want to try the acousticbrainz instead. Update pluginsWithoutDeps as needed to keep preCheck working.
* gvolicon: c04cafb -> 31cf770Benno Fünfstück2016-06-17
|
* Fix lots of fetchgit hashes (fallout from #15469)Tuomas Tynkkynen2016-06-03
|
* rename iElectric to domenkozar to match GitHubDomen Kožar2016-05-17
|
* beets: Merge pull request #15165: Fix ffmpeg callaszlig2016-05-02
|\ | | | | | | | | | | | | This patches the ffmpeg command path so that it will work without ffmpeg being in the user's current path. The commit contains a suggestion from me to patch command_output() instead of just replacing "ffmpeg" so that if a user configuration alters the default commands it will still work.
| * beets: patch ffmpeg invocation in convert pluginProfpatsch2016-05-02
| | | | | | | | | | | | The default convert configuration invokes ffmpeg, so this patches in the right storepath. Since it patches the shlex split, even user config will use the correct path. kudos @aszlig.
* | pnmixer: 2014-07-24 -> 2016-04-23José Romildo Malaquias2016-04-29
|/
* dir2opus: 0.12.1 -> 0.12.2Emery Hemingway2016-04-25
|
* darkice: Fix build due to multiple outputsFranz Pletz2016-04-24
|
* Merge branch 'staging'Vladimír Čunát2016-04-22
|\ | | | | | | | | This includes a fix to closure-size regression that moved share/doc/*/ to share/doc/
| * qastools: move to qmake4HookNikolay Amiantov2016-04-20
| |
* | aucdtect: init at 0.8.2Peter Hoeg2016-04-20
|/ | | | | A binary distribution of the TA Analyzer that verifies if audio files are in fact lossless.
* Merge branch 'master' into closure-sizeVladimír Čunát2016-04-10
|\ | | | | | | | | | | Comparison to master evaluations on Hydra: - 1255515 for nixos - 1255502 for nixpkgs
| * playerctl: 0.4.2 -> 0.5.0Micxjo Funkcio2016-04-04
| |
* | Merge branch 'master' into closure-sizeVladimír Čunát2016-04-01
|\| | | | | | | | | Beware that stdenv doesn't build. It seems something more will be needed than just resolution of merge conflicts.
| * acoustidFingerprinter: fix taglib version checkEmery Hemingway2016-03-17
| |
| * Ensure that we can evaluate the platform attribute of ocaml packages.Nicolas B. Pierron2016-03-13
| |
* | Merge master into closure-sizeVladimír Čunát2016-03-08
|\| | | | | | | | | The kde-5 stuff still didn't merge well. I hand-fixed what I saw, but there may be more problems.
| * Merge pull request #13124 from FRidh/buildPythonApplicationFrederik Rietdijk2016-02-23
| |\ | | | | | | buildPythonApplication: use new function for Python applications
| | * buildPythonApplication: use new function for Python applicationsFrederik Rietdijk2016-02-19
| | |
| * | playerctl: init at 0.4.2Brian McKenna2016-02-22
| |/
* | Merge branch 'master' into closure-sizeVladimír Čunát2016-02-14
|\|
| * beets: Re-enable testsaszlig2016-02-10
| | | | | | | | | | | | | | | | | | | | | | | | | | The reason why the completion tests didn't pass was because we had it already disabled in 2acc258dff1a37974edd6475851e218bb09e281a. Meanwhile, beetbox/beets@a07cb83 has moved the file from test/test_completion.sh to test/rsrc/test_completion.sh. So this has silently re-enabled the completion tests, which we need to investigate on our side why they failed in the first place. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
| * beets: 1.3.16 -> 1.3.17Profpatsch2016-02-09
| | | | | | | | one test fails, see the source comment
| * beets: 1.3.15 -> 1.3.16Profpatsch2016-02-02
| | | | | | | | Add plugins embyupdate, edit, mbsubmit as plugins.
* | treewide: Mass replace 'flac}/bin' to refer the 'bin' outputTuomas Tynkkynen2016-02-01
| |
* | Merge branch 'staging' into closure-sizeVladimír Čunát2016-01-19
|\|
| * ruby: new bundler infrastructureCharles Strahan2015-12-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 #8612
* | Merge branch 'master' into closure-sizeVladimír Čunát2015-12-31
|\| | | | | | | | | TODO: there was more significant refactoring of qtbase and plasma 5.5 on master, and I'm deferring pointing to correct outputs to later.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-26 01:22:59 +0000