This is a regression introduced by my update at e4b7b7b028
Turns out this was actually required to build the package on i686; without it,
the build fails with
```
/nix/store/[...]-flex-2.6.0/lib/libfl.so: undefined reference to `yylex'
```
for some reason ... the easiest solution is to just use flex_2_5_35, which does
build successfully.
* pidgin-osd: init at 0.1.0
A straightforward pidgin plugin; kind of ancient, but still works fine.
* Use autoreconf, which minor hackery around ChangeLog.
Based on @brodul work at
https://github.com/brodul/nixpkgs/tree/arduino-update
Desktop file generation is from #13690
- Solved all download problems. Package/library lists are changing
daily, so I've created my own snapshot of them.
- Prepatch jssc .so inside jar - @brodul mentions that it can be copied
into $HOME while running program.
- Removed some unnecessary dependencies
Tested it by uploading simple sketch to Arduino Uno.
Build the official keybase go client from source. The client includes both a
CLI for performing keybase operations and a service which will start
automatically when needed.
Keybase is a service which combines social proof with encryption. Learn more at
their site: http://keybase.io
fetchMavenArtifact downloads a Maven artifact given a group id, an artifact id,
and a version.
Example usage:
org_apache_httpcomponents_httpclient_4_5_2 = fetchMavenArtifact {
groupId = "org.apache.httpcomponents";
artifactId = "httpclient";
version = "4.5.2";
sha256 = "0ms00zc28pwqk83nwwbafhq6p8zci9mrjzbqalpn6v0d80hwdzqd";
# Optionally: repos = [ ... urls to some Maven repos to use ... ];
# Optionally: url, urls - pointing directly to a specific jar url.
};
Now `org_apache_httpcomponents_httpclient_4_5_2.jar` points to the downloaded
JAR file, while `org_apache_httpcomponents_httpclient_4_5_2` refers to a
derivation that when used used in `buildInputs` will be automatically added to
the Java classpath.
Google Code no longer supports git cloning. We could restore this
revision by exporting the repository to github and working from there,
but barring a request for it, we can just use the released version.
This moves nixos-containers into its own package so that it can be
relied upon by other packages/systems. This should make development
using dynamic containers much easier.