This commit adds `profile-cleaner`.
Use profile-cleaner to reduce the size of browser profiles by organizing
their sqlite databases using sqlite3's vacuum and reindex functions. The
term "browser" is used loosely since profile-cleaner happily works on
some email clients and newsreaders too.
Supported browsers include:
* Aurora
* Chromium (stable, beta, and dev)
* Conkeror
* Firefox (stable, beta, and aurora)
* Google-chrome (stable, beta, and dev)
* Heftig's version of Aurora
* Icedove
* Midori
* Newsbeuter
* Palemoon
* Qupzilla
* Seamonkey
* Thunderbird
* Tor-browser
I'm not adding this to pkgs/development/libraries because it somewhat is
strongly tied to Haxe itself, because otherwise you can't compile to C++
and in the event that someone is going to create something like
"haxePackages" someday it is easier to notice when it's residing in the
Haxe folder.
In theory it would also work by using imperative haxelib, but you'll get
precompiled libraries which need to be patched on NixOS systems. That's
the main reason I was packaging this, among from the fact that even when
patching the libraries, it still leads to occasional library hell and
instabilities.
The package has two outputs: One with the library itself, needed for
compile time ($out) and another one ($lib) which is needed at runtime,
so after compiling, the $out path can be safely garbage collected.
Right now, I've set meta.platforms to Linux only, because that's where
I've tested it. In order to get it running on other platforms the
targetArch attribute has to be set accordingly.
We also build everything completely from scratch, even though there are
binaries within the source ZIP file. The main reason is to make smaller
library dependencies by avoiding bundled libraries and using the ones we
already ship with nixpkgs.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This reverts commit b34a1cc248.
Conflicts:
pkgs/top-level/all-packages.nix
Duplicate package kafka, already existed and used in the nixos service.
Retained the boothead addition to maintainers.
/cc maintainers @codyopel, @fuuzetsu.
Release notes don't indicate any new options or dependencies.
http://git.videolan.org/?p=ffmpeg.git;a=blob;f=RELEASE_NOTES;hb=release/2.6
APIchanges looks like we should be able to replace 2.5 by 2.6
without anything breaking (belongs to staging and needs some testing).
