Commit e37ef92b authored by Guillaume Melquiond's avatar Guillaume Melquiond

Move opam files to opam 2.

parent aafdbf0a
Pipeline #55884 passed with stages
in 63 minutes and 40 seconds
opam-version: "1.2"
opam-version: "2.0"
maintainer: "guillaume.melquiond@inria.fr"
authors: [
"François Bobot"
......@@ -12,7 +12,7 @@ homepage: "http://why3.lri.fr/"
license: "GNU Lesser General Public License version 2.1"
doc: "http://why3.lri.fr/doc/"
bug-reports: "https://gitlab.inria.fr/why3/why3/issues"
dev-repo: "https://gitlab.inria.fr/why3/why3.git"
dev-repo: "git+https://gitlab.inria.fr/why3/why3.git"
tags: [
"deductive"
......@@ -21,12 +21,9 @@ tags: [
"automated theorem prover"
"interactive theorem prover"
]
available: [ ocaml-version >= "4.02.3" ]
build: [
["sh" "-eux" "./run_autoconf_if_needed.sh"] # when used in pinned mode,
# the configure *cannot* yet be
# generated
["./autogen.sh"] {dev} # when pinning, there might be no configure file
["./configure"
"--prefix" prefix
"--disable-why3-lib"
......@@ -38,11 +35,12 @@ build: [
install: [make "install-coq"]
remove: ["rm" "-rf" "%{lib}%/why3/coq"]
remove: ["rm" "-rf" "%{why3:lib}%/coq"]
flags: [ light-uninstall ]
depends: [
"ocaml" {>= "4.02.3"}
"ocamlfind" {build}
"why3"
"coq" {>= "8.5" & < "8.9~"}
......@@ -56,3 +54,12 @@ conflicts: [
"coq-flocq" {< "2.5"}
"coq-flocq" {>= "3.0~"}
]
synopsis: "Why3 environment for deductive program verification"
description: """
Why3 provides a rich language for specification and programming, called WhyML, and relies on external theorem provers, both automated and interactive, to discharge verification conditions. Why3 comes with a standard library of logical theories (integer and real arithmetic, Boolean operations, sets and maps, etc.) and basic programming data structures (arrays, queues, hash tables, etc.). A user can write WhyML programs directly and get correct-by-construction OCaml programs through an automated extraction mechanism. WhyML is also used as an intermediate language for the verification of C, Java, or Ada programs.
Why3 is a complete reimplementation of the former Why platform. Among the new features are: numerous extensions to the input language, a new architecture for calling external provers, and a well-designed API, allowing to use Why3 as a software library. An important emphasis is put on modularity and genericity, giving the end user a possibility to easily reuse Why3 formalizations or to add support for a new external prover if wanted.
This package provides the Coq realizations of Why3 theories."""
opam-version: "1.2"
opam-version: "2.0"
maintainer: "guillaume.melquiond@inria.fr"
authors: [
"François Bobot"
......@@ -12,7 +12,7 @@ homepage: "http://why3.lri.fr/"
license: "GNU Lesser General Public License version 2.1"
doc: "http://why3.lri.fr/doc/"
bug-reports: "https://gitlab.inria.fr/why3/why3/issues"
dev-repo: "https://gitlab.inria.fr/why3/why3.git"
dev-repo: "git+https://gitlab.inria.fr/why3/why3.git"
tags: [
"deductive"
......@@ -21,12 +21,9 @@ tags: [
"automated theorem prover"
"interactive theorem prover"
]
available: [ ocaml-version >= "4.02.3" ]
build: [
["sh" "-eux" "./run_autoconf_if_needed.sh"] # when used in pinned mode,
# the configure *cannot* yet be
# generated
["./autogen.sh"] {dev} # when pinning, there might be no configure file
["./configure"
"--prefix" prefix
"--disable-why3-lib"
......@@ -39,19 +36,29 @@ build: [
install: [make "install-ide"]
remove: [
["rm" "-f" "%{lib}%/why3/commands/why3ide"]
["rm" "-rf" "%{share}%/why3/images"]
["rm" "-f" "%{why3:lib}%/commands/why3ide"]
["rm" "-rf" "%{why3:share}%/images"]
]
flags: [ light-uninstall ]
depends: [
"ocaml" {>= "4.02.3"}
"ocamlfind" {build}
"why3"
"lablgtk"
("lablgtk" | "lablgtk3")
"conf-gtksourceview"
]
conflicts: [
"lablgtk" {< "2.14.2"}
]
synopsis: "Why3 environment for deductive program verification"
description: """
Why3 provides a rich language for specification and programming, called WhyML, and relies on external theorem provers, both automated and interactive, to discharge verification conditions. Why3 comes with a standard library of logical theories (integer and real arithmetic, Boolean operations, sets and maps, etc.) and basic programming data structures (arrays, queues, hash tables, etc.). A user can write WhyML programs directly and get correct-by-construction OCaml programs through an automated extraction mechanism. WhyML is also used as an intermediate language for the verification of C, Java, or Ada programs.
Why3 is a complete reimplementation of the former Why platform. Among the new features are: numerous extensions to the input language, a new architecture for calling external provers, and a well-designed API, allowing to use Why3 as a software library. An important emphasis is put on modularity and genericity, giving the end user a possibility to easily reuse Why3 formalizations or to add support for a new external prover if wanted.
This package provides an IDE for Why3."""
opam-version: "1.2"
opam-version: "2.0"
maintainer: "guillaume.melquiond@inria.fr"
authors: [
"François Bobot"
......@@ -12,7 +12,7 @@ homepage: "http://why3.lri.fr/"
license: "GNU Lesser General Public License version 2.1"
doc: "http://why3.lri.fr/doc/"
bug-reports: "https://gitlab.inria.fr/why3/why3/issues"
dev-repo: "https://gitlab.inria.fr/why3/why3.git"
dev-repo: "git+https://gitlab.inria.fr/why3/why3.git"
tags: [
"deductive"
......@@ -21,12 +21,9 @@ tags: [
"automated theorem prover"
"interactive theorem prover"
]
available: [ ocaml-version >= "4.02.3" ]
build: [
["sh" "-eux" "./run_autoconf_if_needed.sh"] # when used in pinned mode,
# the configure *cannot* yet be
# generated
["./autogen.sh"] {dev} # when pinning, there might be no configure file
["./configure"
"--prefix" prefix
"--disable-frama-c"
......@@ -34,24 +31,25 @@ build: [
"--disable-js-of-ocaml"
"--disable-ide"]
[make "-j%{jobs}%" "all" "opt" "byte"]
[make "doc" "stdlibdoc" "apidoc"] {with-doc}
]
install: [make "install" "install-lib"]
install: [
[make "install" "install-lib"]
[make "DOCDIR=%{_:doc}%" "install-doc"] {with-doc}
]
remove: [
["rm" "%{bin}%/why3"]
["rm" "-r" "%{lib}%/why3"]
["rm" "-r" "%{share}%/why3"]
["rm" "%{_:bin}%/why3"]
["rm" "-r" "%{_:lib}%"]
["rm" "-r" "%{_:share}%"]
["rm" "-r" "%{_:doc}%"] {with-doc}
]
flags: [ light-uninstall ]
build-doc: [
[make "doc" "stdlibdoc" "apidoc"]
[make "DOCDIR=%{doc}%/why3" "install-doc"]
]
depends: [
"ocaml" {>= "4.02.3"}
"ocamlfind" {build}
"menhir" {>= "20151112"}
"num"
......@@ -67,3 +65,10 @@ conflicts: [
"why3-base"
"ocamlgraph" {< "1.8.2"}
]
synopsis: "Why3 environment for deductive program verification"
description: """
Why3 provides a rich language for specification and programming, called WhyML, and relies on external theorem provers, both automated and interactive, to discharge verification conditions. Why3 comes with a standard library of logical theories (integer and real arithmetic, Boolean operations, sets and maps, etc.) and basic programming data structures (arrays, queues, hash tables, etc.). A user can write WhyML programs directly and get correct-by-construction OCaml programs through an automated extraction mechanism. WhyML is also used as an intermediate language for the verification of C, Java, or Ada programs.
Why3 is a complete reimplementation of the former Why platform. Among the new features are: numerous extensions to the input language, a new architecture for calling external provers, and a well-designed API, allowing to use Why3 as a software library. An important emphasis is put on modularity and genericity, giving the end user a possibility to easily reuse Why3 formalizations or to add support for a new external prover if wanted."""
Why3 environment for deductive program verification.
Why3 provides a rich language for specification and programming, called
WhyML, and relies on external theorem provers, both automated and
interactive, to discharge verification conditions. Why3 comes with a
standard library of logical theories (integer and real arithmetic,
Boolean operations, sets and maps, etc.) and basic programming data
structures (arrays, queues, hash tables, etc.). A user can write WhyML
programs directly and get correct-by-construction OCaml programs
through an automated extraction mechanism. WhyML is also used as an
intermediate language for the verification of C, Java, or Ada
programs.
Why3 is a complete reimplementation of the former Why platform. Among
the new features are: numerous extensions to the input language, a new
architecture for calling external provers, and a well-designed API,
allowing to use Why3 as a software library. An important emphasis is
put on modularity and genericity, giving the end user a possibility to
easily reuse Why3 formalizations or to add support for a new external
prover if wanted.
This package provides the Coq realizations of Why3 theories.
Why3 environment for deductive program verification.
Why3 provides a rich language for specification and programming, called
WhyML, and relies on external theorem provers, both automated and
interactive, to discharge verification conditions. Why3 comes with a
standard library of logical theories (integer and real arithmetic,
Boolean operations, sets and maps, etc.) and basic programming data
structures (arrays, queues, hash tables, etc.). A user can write WhyML
programs directly and get correct-by-construction OCaml programs
through an automated extraction mechanism. WhyML is also used as an
intermediate language for the verification of C, Java, or Ada
programs.
Why3 is a complete reimplementation of the former Why platform. Among
the new features are: numerous extensions to the input language, a new
architecture for calling external provers, and a well-designed API,
allowing to use Why3 as a software library. An important emphasis is
put on modularity and genericity, giving the end user a possibility to
easily reuse Why3 formalizations or to add support for a new external
prover if wanted.
This package provides an IDE for Why3.
#!/bin/sh -eux
if [ ! -f "configure" ]; then
autoconf
automake --add-missing || true
fi
Why3 environment for deductive program verification.
Why3 provides a rich language for specification and programming, called
WhyML, and relies on external theorem provers, both automated and
interactive, to discharge verification conditions. Why3 comes with a
standard library of logical theories (integer and real arithmetic,
Boolean operations, sets and maps, etc.) and basic programming data
structures (arrays, queues, hash tables, etc.). A user can write WhyML
programs directly and get correct-by-construction OCaml programs
through an automated extraction mechanism. WhyML is also used as an
intermediate language for the verification of C, Java, or Ada
programs.
Why3 is a complete reimplementation of the former Why platform. Among
the new features are: numerous extensions to the input language, a new
architecture for calling external provers, and a well-designed API,
allowing to use Why3 as a software library. An important emphasis is
put on modularity and genericity, giving the end user a possibility to
easily reuse Why3 formalizations or to add support for a new external
prover if wanted.
#!/bin/sh -eux
if [ ! -f "configure" ]; then
autoconf
automake --add-missing || true
fi
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment