-
-
Notifications
You must be signed in to change notification settings - Fork 15.5k
clips: 6.30 -> 6.31 #109914
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
clips: 6.30 -> 6.31 #109914
Conversation
pname = "clips"; | ||
src = fetchurl { | ||
url = "mirror://sourceforge/clipsrules/CLIPS/6.30/clips_core_source_630.tar.Z"; | ||
sha256 = "1r0m59l3mk9cwzq3nmyr5qxrlkzp3njls4hfv8ml85dmqh7n3ysy"; | ||
url = "mirror://sourceforge/clipsrules/CLIPS/6.31/clips_core_source_630.tar.Z"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
url = "mirror://sourceforge/clipsrules/CLIPS/6.31/clips_core_source_630.tar.Z"; | |
url = "mirror://sourceforge/clipsrules/CLIPS/6.31/clips_core_source_631.tar.Z"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should try to derive that fragment from the version to support auto update.
I started to look into this, but after fixing the URL and hash, it doesn't compile – I guess because they moved things around. Don't have time to look further right now but I can investigate in a day or two.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I got clips-6.31 to build and run, but it doesn't seem like I can push to this PR, or to the auto-update/clips branch. Here's the replacement file. It also derives the URL from the version number.
{ stdenv, fetchurl }:
stdenv.mkDerivation rec {
version = "6.31";
pname = "clips";
src = let v = builtins.replaceStrings [ "." ] [ "" ] version;
in fetchurl {
url =
"mirror://sourceforge/clipsrules/CLIPS/${version}/clips_core_source_${v}.tar.gz";
sha256 = "165k0z7dsv04q432sanmw0jxmxwf56cnhsdfw5ffjqxd3lzkjnv6";
};
buildPhase = ''
make -C core
'';
installPhase = ''
install -D -t $out/bin core/clips
'';
meta = with stdenv.lib; {
description = "A Tool for Building Expert Systems";
homepage = "http://www.clipsrules.net/";
longDescription = ''
Developed at NASA's Johnson Space Center from 1985 to 1996,
CLIPS is a rule-based programming language useful for creating
expert systems and other programs where a heuristic solution is
easier to implement and maintain than an algorithmic solution.
'';
license = licenses.publicDomain;
maintainers = [maintainers.league];
platforms = platforms.linux;
};
}
I will push it after doing a little clean up. |
4a5eca5
to
f0c2229
Compare
@league it would be great if you could take another look. |
f0c2229
to
065ffc2
Compare
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/clips/versions.
meta.description for clips is: "A Tool for Building Expert Systems"
meta.homepage for clips is: "http://www.clipsrules.net/"
meta.changelog for clips is: ""
Updates performed
To inspect upstream changes
Impact
Checks done (click to expand)
built on NixOS
The tests defined in
passthru.tests
, if any, passed0 of 0 passed binary check by having a zero exit code.
0 of 0 passed binary check by having the new version present in output.
directory tree listing: https://gist.github.com/6cf425a4f5a56bfc34bde50a810fcd6a
du listing: https://gist.github.com/9fdcb837524269f76bc9715d285e2e64
Rebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from Cachix:
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the
trusted-users
list or you can usesudo
since root is effectively trusted.Or, build yourself:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of
nixpkgs-review
run on x86_64-linux 11 package built:
Maintainer pings
cc @league for testing.