diff options
| author | Bjørn Forsman <bjorn.forsman@gmail.com> | 2015-02-15 14:57:16 +0100 |
|---|---|---|
| committer | Bjørn Forsman <bjorn.forsman@gmail.com> | 2015-10-23 09:44:07 +0200 |
| commit | e8c22b33e6ca0d4b298f0a7dcb4208c0cbeb3ddf (patch) | |
| tree | 689284b93e69036a2868136dfa14ff77e9acceed /pkgs/development/python-modules/GitPython/hardcode-git-path.patch | |
| parent | a924c55d0b868c7e9eb88934afcb477715e09c68 (diff) | |
baudline: init at 1.0.8
Baudline is a scientific signal analysis application.
I was unsure whether the baudline license allowed packaging in nixpkgs,
so I sent a copy of this nix expression (and some explanation) to their
support. I got this reply:
From: Erik Olson <erik@sigblips.com>
Subject: Re: Licensing question
Hello Bjorn,
This sounds fine. What you suggest doing is very similar to how the
FreeBSD FreshPorts system deals with baudline.
Erik
So basically, everything is good as long as we only distribute the _expression_
to install the package. We must not distribute the package (binary).
Diffstat (limited to 'pkgs/development/python-modules/GitPython/hardcode-git-path.patch')
0 files changed, 0 insertions, 0 deletions