This branch updates node to 0.10.8, as well as updating its
dependencies. It also updates node-packages to use the new style
generated by npm2nix (some packages may have been lost in the switch,
please check!).
Note that 0.10 had some backwards-compatability breaks with 0.8,
particularly for readable streams. Please see the official documentation
for migration help.
Note that I have not yet tested this on darwin (node.js was already
broken there), but will do so soon and fix it if it's broken.
Signed-off-by: Shea Levy <shea@shealevy.com>
Starting with 1.0.0 (which is not released at the time of this commit
but will be before it is pushed), npm2nix takes a JSON file with a list
of names (and optionally version ranges) and generates a data-only (no
functions, no rec, no let, etc.) nix expression representing the
packages with those names and their dependencies.
node-packages.nix now builds its package list from that generated
expression. If a package needs native dependencies as build inputs, they
can be added to the nativeDeps attribute set. If a package cannot be
generated by npm2nix for some reason, it can be added manually to the
set.
I tried to capture the packages represented by the previous
node-packages.nix in the new node-packages.json, but I almost certainly
missed some that will have to be added manually.
Signed-off-by: Shea Levy <shea@shealevy.com>
This reverts commit 8f7cfc0c7370e2b46a7692cc953ff7a43411d5d6, reversing
changes made to cc85ad4b1c365533049ec4af7adee0fe7c83c7b8.
The merge changed stdenv (a bit surprisingly, see #555 for details).
Actually, Gajim can use notifications through dbus if notification-daemon is
available. Otherwise it falls back to notify-python, which is why I disabled it
by default, especially because upstream support of that Python library isn't
especially awesome ;-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
There is no new upstream version available and the latest upstream release is
still using calls to prehistoric versions of libnotify. Most other distro have
patched this already, so no need to patch again. Patch is from Fedora (which is
the most referenced source seen so far).
Additionally the configure script cannot find the correct path to the codegen
executable, so we're patching it accordingly as well.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This needed a bit of patching the paths to the latex and dvipng executables.
In addition, we also address a small bug by using sed:
tmpfd, tmppng = mkstemp(prefix='gajim_tex', suffix='.png')
tmpfd.close()
This obviously won't work, because mkstemp() actually returns a file descriptor
_number_ and not a Python file object.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Use a patch from Arch Linux to use drill instead of nslookup. The primary reason
for this is because nslookup is in bind, and we don't want to depend on the
whole bind package just for the sake of supporting SRV lookups.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Drill is a lightweight DNS lookup command using ldns, which we are going to use
in Gajim, to avoid a dependency on bind.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This brings in Chromium 27 as the new stable version.
Specific versions of the updated channels:
stable: 26.0.1410.63 -> 27.0.1453.93 (builds fine, tested)
beta: 27.0.1453.81 -> 28.0.1500.20 (builds fine, tested)
dev: 28.0.1500.11 -> 29.0.1516.3 (builds fine, tested)
We now can finally drop the following patches:
* glibc-2.16-use-siginfo_t.patch
* pulseaudio_array_bounds.patch
These were for version 26 only and thus are no longer needed.
In addition, we no longer have to use the pre/post attributes, as there is just
_one_ place that uses version specific stuff (path to webcore.gyp).
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Wanted to do this a long time ago, but never had a reason to do it. But with
Chromium 29 having no make target for chrome_sandbox, we now use ninja as well
as the official build and most other distributions.
The whole build/make flags cruft is now integrated into one buildPhase override
and we just call ninja there by exporting the specific variables.
And this also makes enableParallelBuilding obsolete, as we use NIX_BUILD_CORES
directly now.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Actually a "*[0-9]" wildcard isn't enough for some unrelated icons to slip into
the derivation output, so let's explicitely check again within the for loop.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This fixes the following bugs:
* traceback on decryption of OpenPGP-encrypted messages
* remote_control: use GED in send_chat_message
* gajim-0.15.3 can't connect to server without StartTLS support
* "make check" fails with complaining on src/command_system/mapping.py
* Account Wizard: Make text selectable
* Gajim crashes in connect.py
Overview and details:
https://trac.gajim.org/query?status=closed&milestone=0.15.4
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This should clean up the package expression significantly by actually using
explicit input attributes and setting PYTHONPATH and GST_PLUGIN_PATH from
environment variables in the builder.
In addition, this adds a small patch from the upstream Mercurial repository to
add an index.theme to the icons, so Gajim is able to load them correctly from
the store.
With this change, I'm adding myself to the maintainers list as well, because I'm
switching over from TKabber to Gajim.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
I removed darwin-specific bits, as I can't test them right now. If
it's broken, let me know and I'll fix on darwin.
Signed-off-by: Shea Levy <shea@shealevy.com>
