Differences

This shows you the differences between two versions of the page.

--- tools:cpm [2017-04-25 15:23] – [Uploading and Publishing Packages] mh
+++ tools:cpm [2018-11-27 10:12] – mh
@@ Line 20: / Line 20: @@
 the same package.
-The [[http://www-ps.informatik.uni-kiel.de/~mh/curry/cpm.cgi | currently available packages]]
+===== Available Packages =====
-can immediately be downloaded or installed when CPM is installed (see below).
-Using CPM, one can also obtain more detailed information about
+There are more than [[http://www.informatik.uni-kiel.de/~curry/cpm/ | 90 packages available]]
-individual packages.
+(including more than 600 modules).
+There is a [[http://www.informatik.uni-kiel.de/~curry/cpm/ | table of all packages]]
+with more detailed information (e.g., API documentation).
+These packages can immediately be downloaded or installed when CPM is installed (see below).
@@ Line 29: / Line 32: @@
 CPM is already part of recent distributions of the Curry systems
-PAKCS (Version 1.14.3 or higher) and KiCS2 (Version 0.5.2 or higher).
+[[http://www.informatik.uni-kiel.de/~pakcs/|PAKCS]] (Version 1.15.0 or higher) and
+[[http://www-ps.informatik.uni-kiel.de/kics2/|KiCS2]] (Version 0.6.0 or higher).
 If you have some older version of PAKCS or KiCS2, you can also
 install CPM from its public repository.
@@ Line 43: / Line 47: @@
 > make
-If this was successful, the binary ''cpm'' has been generated in the
+If this was successful, the binary ''cypm'' has been generated in the
 directory ''~/.cpm/bin''. This is also the directory where CPM installs binaries
-of tools distributed with packages. For convenient use, you should add the
+of applications distributed as packages. For convenient use, you should add the
 directory ''~/.cpm/bin'' to your path. Alternatively, you can also put
-the binary ''~/.cpm/bin/cpm'' somewhere in your path or create a symbolic
+the binary ''~/.cpm/bin/cypm'' somewhere in your path or create a symbolic
 link from some path directory to this binary.
@@ Line 54: / Line 58: @@
 Now you can clone a copy of the central package index repository by
-    > cpm update
+    > cypm update
 Afterwards, you can show a short list of all packages in this index by
-    > cpm list
+    > cypm list
 The command
-    > cpm info PACKAGE
+    > cypm info PACKAGE
 can be used to show more information about a package.
@@ Line 71: / Line 75: @@
 Therefore, to initialize it and use other packages, you need
 a package description file in some project directory.
-All this can be created by the command ''cpm new'':
+All this can be created by the command ''cypm new'':
-    > cpm new myproject
+    > cypm new myproject
 This command creates a new project directory ''myproject''
 containing an initial package description file ''package.json''
 and a subdirectory ''src'' (together with other template files).
-If you need some other package for your project,
+Change into the new project directory:
-add it as a dependency in ''package.json''.
+    > cd myproject
+If you need some other packages for your project,
+add them as a dependency in ''package.json''.
 Then run
-    > cpm install
+    > cypm install
 to install all dependencies of the current package.
 Afterwards, start your interactive Curry environment by
-    > cpm curry
+    > cypm curry
 and you will be able to load the modules of the current package
@@ Line 94: / Line 102: @@
 so that you can directly load any program you have stored
 in this directory.
+For instance, if the module ''Main.curry'' is stored in the
+directory ''src'', you can load it into your Curry system
+(e.g., KiCS2 or PAKCS) by
+    > cypm curry :load Main
 ===== Manual and Further Documentation =====

/srv/dokuwiki/currywiki/data/pages/tools/cpm.txt · Last modified: 2020-03-14 18:06 by mh

Back to top