| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Regression introduced by f91dacdd07731e06cec80b727b28b749e64f60e8.
Accidentally thought that it's compiling with XRandR support enabled,
because the cmake output said so:
Looking for XRRQueryExtension in Xrandr - found
Unfortunately, despite this message, the relevant part is:
Looking for XRRNotifyEvent - not found
So, ea4afb7 still holds true and I've added a small comment to avoid
this from happening in the future.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
| |
I don't know what a "mouse keyboard" is, but instead of fixing the
description, let's use the one from the upstream README file, which is
also shorter than what we previously had.
The homepage http://synergy-foss.org/ is outdate since ages, so let's
point to the new site.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Quite a lot of upstream changes happened in between, so here are the
upstream changes:
https://github.com/synergy/synergy/releases/tag/1.7.0
https://github.com/synergy/synergy/releases/tag/v1.7.1-stable
https://github.com/synergy/synergy/releases/tag/v1.7.2-stable
https://github.com/synergy/synergy/releases/tag/v1.7.3-stable
https://github.com/synergy/synergy/releases/tag/v1.7.4-stable
The upstream project has stopped using cryptopp
(synergy/synergy@80343c4) and now uses OpenSSL instead (see issue
synergy/synergy#4313) so we no longer need our patch.
Also, the issue for the 'install' target has been closed as obsolete and
although they had such a target in the meantime, it has been removed
again in synergy/synergy@d1eb7a6, so let's not rely on it anymore and
remove the comment on the closed/obsolete issue.
Forcing support for XRandR in the CMakeLists.txt file isn't needed
anymore, because the issues mentioned in ea4afb7 have been fixed
upstream.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Reported-by: devhell <"^"@regexmail.net>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Overview of the updated versions:
beta: 45.0.2454.15 -> 45.0.2454.26
dev: 45.0.2454.15 -> 46.0.2471.2
Changes for getting beta and dev channel to build:
* The reference for chrome::FILE_FLASH_PLUGIN doesn't exist anymore in
version 46, because it has been dropped upstream, see the following
review URL:
https://codereview.chromium.org/1255943002
We set the PPAPI Flash path using a command line flag anyway, so it
doesn't hurt us if we don't patch that path (which was an old
artifact from the NSAPI->PPAPI conversion anyway).
Changes for the dev channel only:
* It seems that in the SCM, chrome/test/data/webui/ contains a lot of
files, however they are missing in the tarball.
This has been reported upstream at: https://crbug.com/515917
Our fix is to just not include webui/i18n_process_css_test.html at
all, to avoid the configure (gyp) phase to fail, because we're not
building tests anyway.
All channels built and tested by my Hydra instance at:
https://headcounter.org/hydra/eval/218978
Test reports:
x86: https://headcounter.org/hydra/build/723341/download/1/log.html
x86_64: https://headcounter.org/hydra/build/723342/download/1/log.html
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
| |
Some plugin bundles must be unpacked when used in Eclipse. With this
change the plugin manifest is checked for the setting indicating that
unpacking should happen.
|
| |
|
|
|
|
|
|
| |
Simplifies `buildEclipsePlugin` and `buildEclipseUpdateSite` functions
such that they require only absolutely necessary arguments. Also
add/expand comments slightly.
|
|
|
|
|
|
| |
It does not really make sense to install the plugin packages directly as
they are intended for use with `eclipseWithPlugins`. Therefore it is
best not to present them to users as such.
|
| |
|
|
|
|
|
| |
This makes these builder functions available for use outside the file.
That is, plugins can be defined out-of-tree.
|
|
|
|
|
|
| |
This function provides functionality common to all Eclipse plugin
builders. In particular, it sets a package name and flags the derivation
as an Eclipse plugin.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Also add helper function for building packages from downloaded Eclipse
update site.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This commit also introduces some infrastructure surrounding Eclipse
plugins.
|
|
|
|
|
| |
This function allows installation of a given Eclipse with a given list
of Eclipse plugins.
|
| |
|
|
|
|
|
| |
Adds pidgin-opensteamworks, a Pidgin plugin to add support for the
Steam Friends/Steam IM service
|
|\
| |
| | |
x42-plugins : 2014-11-01 -> 2015-07-02
|
| | |
|
|\ \
| | |
| | | |
ardour: 4.0 -> 4.1
|
| |/ |
|
| | |
|
|\ \
| | |
| | | |
ir.lv2 : fix $out creation
|
| |/ |
|
|\ \
| | |
| | | |
gpodder: 3.8.3 -> 3.8.4
|
| | | |
|
|\ \ \
| |/ /
|/| | |
bar: 1.0 -> 1.1
|
| |/ |
|
|/ |
|
|
|
|
|
|
|
| |
I think the previous name comes from the fact that some older versions
were distributed in tarballs named ng-spice-rework-<version>. But now
the "rework" name seems odd; most references I found on the internet
calls the package "ngspice". Fix it.
|
| |
|
| |
|
| |
|
|\
| |
| | |
thunderbird: 31.7.0 -> 38.1.0
|
| | |
|
|\ \
| | |
| | | |
mupdf: desktop file fix
|
| | | |
|
|\ \ \
| | | |
| | | | |
Add new package git-crypt
|
| | | | |
|
| | | | |
|
|/ / / |
|
| | | |
|