| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
I'm including the whole file here, because it's easier to move it to
<nixpkgs> once version 0.9.0 is finally released.
This finally gets rid of the damn phonon dependency which cased most of
my playback issues so far.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
|
| |
This was in since the initial commit (6c224e4) of the bfqsched Nix
expression and I didn't notice it for all those upgrades.
Basically, this is just a no-op, because nowadays the sed expression
doesn't rewrite anything anymore, but it might be harmful if it should
match something in a future version of the bfqsched patch set.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We also now use fetchFromGitHub and no longer use "git rev-parse" in
order to truncate the commit hash. Instead, we're just trimming down the
revision we already have in the Nix expression to 7 characters (like per
default if done by "git rev-parse --short").
This should also mitigate the evaluation problems with latest nixpkgs,
where leaveDotGit changed so it results in a different hash.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Changes for v7r7:
* BUGFIX: Prevent the OOM queue from being involved in the queue
cooperation mechanism. In fact, since the requests temporarily
redirected to the OOM queue could be redirected again to dedicated
queues at any time, the state needed to correctly handle merging with
the OOM queue would be quite complex and expensive to maintain.
Besides, in such a critical condition as an out of memory, the
benefits of queue merging may be little relevant, or even negligible.
* IMPROVEMENT: Let the OOM queue be initialized only once. Previously,
the OOM queue was reinitialized, at each request enqueue, with the
parameters related to the process that issued that request.
Depending on the parameters of the processes doing I/O, this could
easily cause the OOM queue to be moved continuously across service
trees, or even across groups. It also caused the parameters of the
OOM queue to be continuously reset in any case.
* CODE IMPROVEMENT. Performed some minor code cleanups, and added some
BUG_ON()s that, if the weight of an entity becomes inconsistent,
should better help understand why.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
| |
The latter is a newly introduced (well... not exactly introduced but
actually referenced, I think it was there before) dependency of
nixAddon.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
| |
We now no longer override the package included in <nixpkgs>, but build
it completely from the upstream Git repository and do our patches right
after the fetchgit.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
| |
Basically this is just an old script I wrote to separate and merge color
information from the actual ASCII arts.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
| |
Although we're building for 3.18, the patch should still apply.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
| |
Just threw me out of zone, because I was terribly annoyed on why the
hell Python indentation isn't done correctly anymore. If the file path
is something like "indent/script4316.vim", Vim won't load it because
it's searching for "indent/$ftname.vim".
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
| |
The plugins "vim-haxe" and "vim-addon-nix" need this dependency.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
|
| |
The main reason for doing this is to avoid collisions with other vim
variants in <nixpkgs> which are expecting an .override attribute.
Moving it into pkgs/ entirely also has the advantage of being properly
namespaced rather than "all over the place" and we also don't clash
anymore with existing Vim packages.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
| |
Includes a patch for 3.17-rc1 from:
https://groups.google.com/forum/#!topic/bfq-iosched/piEzoNMGmk8
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I found "nixconf" a little big too generic and thus not unlikely enough
to someday collide with something in <nixpkgs>. That's why I chose the
name "vuizvui" as a Bavarion word (actually _two_ words: "vui zvui") for
"far too much", in terms of the opposite of "nix" - which means
"nothing".
A possible downside for choosing this name is that it might be
jawbreaker to some English native speakers out there, but I don't really
care if the pronunciation is correct nor do I expect to get a lot of
public attention on this repository.
And yes, for English native speakers, a pronunciation like "fui-tsui" is
probably okay as well :-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
| |
This is going to be needed as the main application for my lighting
laptop :-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 83ba20511bf553d2dd395a6fe4af73fc9d86d57c.
We now have nbxmpp in upstream <nixpkgs>, so we no longer need it in our
own overrides and there was a new tarball release issued upstream just
one day after we did that override, so let's move over to using this one
instead.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Conflicts:
overrides/default.nix
pkgs/gajim/0.16-pre.nix
pkgs/nbxmpp/default.nix
|
| |
|
|
|
|
|
| |
This is already included in upstream <nixpkgs>, so we no longer need to
let it rot here.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
| |
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
| |
|
|
|
|
|
|
|
| |
This is basically just a shell script that feeds the right command line
switches into ffmpeg. And yes, it is a mess, as I was experimenting with
it a bit, so the implementation is more or less just for preserving
history ;-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
Those packages aren't actually overrides and thus it doesn't make sense
to categorize them into "overrides".
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
