Consider this as a first step towards the integration of Qt5 into nixpkgs,
it does not yet intends to replace Qt4 on every packages even if possible.
My goal here is to have a first derivation in common between people who
needs qt5 for development purposes.
The derivation has been written from scratch but I took care to read at the
version 4 to re-integrate some patches which are still compatible. However,
I did not had enough time to test gtkStyle and flashplayerFix as I do not
use any of them. Also, OSX users will have to do some extra work because
I do not have any mac.
Finally, as some configure flags have changed and in an hope to provide a
clear package definition before it becomes mature, I voluntary added some
flags which are default. Once every option will be mastered, we will just
have to redo a pass on qt5 configure flags and remove the ones which are
set by default.
To give the ability to use a different Qt version than the default one
(which can build 3 different times Qt Libraries if we mixed the default
one, the qtcreator one and the version including all the examples and the
docs).
Right now a developer can choose to directly install the QtSDK which
includes a "full" (developerBuild + docs + examples) Qt version and uses
it to build QtCreator.
The possibility to only install QtCreator and its previous behavior has
been kept for flexibility purposes (we do not need to force someone on the
SDK approach).
FriBID is an open source software for the Swedish e-id system called
BankID. FriBID also supports processor architectures and Linux/BSD
distributions that the official software doesn't support.
https://fribid.se/index.en.html
FriBID plugin is a firefoxWrapper plugin. Enabled by setting:
nixpkgs.config.enableFriBIDPlugin = true
Kept the old hacks where they don't break the build in case they things
they fix are still relevant.
I checked that the upgrade doesn't break:
1) Asymptote and EProver builds.
2) My XeLaTeX demo from configurations/ repository.
3) Some of my own files.
The upgrade fixes problems with simultaneous use of 3D and LaTeX labels
in Asymptote.
Please provide a test that worked previously and is broken now if you
need to revert this update or its parts.
Features:
+ configurable via environment variables
+ can skip the actual launching of the lisp implementation (source it
with NIX_LISP_SKIP_CODE=1 to get all the settings)
+ currently supports SBCL, CLisp, ECL
+ determines lisp implementation from NIX_LISP_COMMAND variable or
from buildInputs
+ sets ASDF search path for packages using buildInputs
Somehow Dwarf Fortress suddenly started failing to use our libpng (or
zlib). I tried all possible combinations (supplying them via
LD_LIBRARY_PATH in the script) but it just won't work.
This solution was found in the Archlinux bug tracker: It just symlinks
all problematic .png files to their .bmp counterparts. It's ugly and
*sadly* breaks tileset support (unless you convert them to bmp) but I
think it's acceptable, as the whole expression is pretty problematic
in terms of purity.
Let's hope the next release of Dwarf Fortress will be easier to
support.
(fixes#710)
The current asciidoc expression is impure; it relies on several tools to
be found in PATH at runtime. This commit adds a enableStandardFeatures
parameter that, if true, pulls in all dependencies and patches asciidoc
to contain full paths to the tools.
I've set enableStandardFeatures = false for the existing asciidoc
attribute so that the closure size stays unchanged, at 255 MiB. The new
asciidocFull attribute (with enableStandardFeatures = true) has a
closure size of 1.5 GiB.
imagemagick, transfig, inkscape, fontconfig and ghostscript are missing
dependencies of dblatex. Instead of adding all those dependencies to the
existing dblatex attribute, make a new dblatexFull attribute for that.
Also pass --use-python-path at install time so that script shebangs end
up with #!/path/to/python instead of #!/path/to/env python (which is
impure when not run in a wrapper).
This introduces the following changes:
- Remove scraping of the Robot web interface for getting the server ID.
- Display server number whenever appropriate.
- Remove duplicate definition of exceptions.
- Gracefully return if there are no subnets available.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This reverts commit 58fdf34296, because it
wasn't actually very fitting for nixpkgs in general, so let's wait for
the upcoming upstream release to address this.
Details can be found at:
https://github.com/NixOS/nixpkgs/commit/58fdf34#commitcomment-4231461
Thanks to @iElectric for the notice.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
The upstream package has a new maintainer (Jeff Forcier) and thus the
main homepage for the project is the GitHub page.
Also the long description contains quite a lot of unrelevant
information, so I've used the one from PyPI, which is a lot smaller and
just contains what the library supports and does.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This patch should be backwards-incompatible and is also submitted
upstream as paramiko/paramiko#218.
The main reason for this patch is that we need it for NixOS/nixops#124
in order to cope with NixOS/nixops@a2718b6, which makes ECDSA private
key the default for new deployments.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
A small summary of the changes:
- Add tentative support for ECDSA keys.
- Add server-side support for the SSH protocol's 'env' command.
The full change log can be found at:
https://github.com/aszlig/paramiko/blob/master/NEWS
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This is needed for the latest Paramiko release, which includes support
for ECDSA keys using this library.
I'm using ECDSA in the description itself, because the name also
reflects the functionality and "cryptographic signature library" would
sound odd in this case.
Also, I'm adding myself to maintainers, because I'm going to take over
maintenance for Paramiko as well.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This reverts commit aef81d6eb6.
It's really not good to have every little package that depends on
asciidoc to pull in 1.5 GiB in dependencies (such as Lilypond).
The current asciidoc expression is impure; it relies on several tools to
be found in PATH at runtime. This commit adds a enableStandardFeatures
parameter that pulls in all dependencies and patches asciidoc to contain
full paths to the tools.
enableStandardFeatures defaults to true because asciidoc may attempt to
call all tools in its default configuration. With all standard features,
the closure size increases from 255 MiB to 1.5 GiB. Set
enableStandardFeatures = false if you want a minimal asciidoc.
This fixes a few issues with symlinks and also needs to be up to date
because we're going to use it for building Chromium instead of the
bundled GYP that comes with Chromium.
Also, the package was missing a license and in the current revision, we
also have test cases, so let's enable them.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
