@@ -54,22 +54,23 @@ resulting behavior must be functionally equivalent.
54
54
55
55
56
56
57
- ## xPacks
57
+ ## What are xpm packages? ( xPacks)
58
58
59
- ** xPacks** (short for ** xpm packages** ) are general-purpose,
60
- language-neutral software packages.
59
+ ** xpm packages** , abbreviated as ** xPacks** , are versatile,
60
+ language-neutral software packages. They have been successfully
61
+ utilised in C/C++ projects.
61
62
62
63
<details >
63
- <summary >What the heck are xPacks? Please, do not introduce another package format!</summary >
64
+ <summary >What the heck are xpm packages / xPacks? Please, do not introduce another package format!</summary >
64
65
65
- While the initial appearance may seem complex, utilizing xPacks
66
- ( xpm packages) is, in fact, straightforward.
66
+ While the initial appearance may seem complex, utilizing
67
+ xpm packages is, in fact, straightforward.
67
68
The design rationale is to automate frequent
68
69
operations that occur during software development, in this case the
69
70
installation of
70
71
dependencies, and to ensure reproducibility.
71
72
72
- xPacks are managed by ** [ xpm] ( https://xpack.github.io/xpm/ ) **
73
+ These packages are managed by ** [ xpm] ( https://xpack.github.io/xpm/ ) **
73
74
(the xPack Project Manager),
74
75
a program that complements the ** [ npm] ( https://docs.npmjs.com/cli/ ) ** CLI
75
76
(the popular JavaScript package manager), with new language-neutral features.
@@ -84,7 +85,7 @@ same repositories as **npm**, whether public or private.
84
85
The packages (usually regular archives, but also git repositories),
85
86
are extracted into separate folders within the project.
86
87
87
- Based on the content, there are two types of packages:
88
+ Based on the content, there are two types of xpm packages:
88
89
89
90
- ** source packages** (that install source files, usually libraries) and
90
91
- ** binary packages** (that install executables/binary files, usually tools).
@@ -102,8 +103,8 @@ archives, the packages are extracted only once into a user global location to
102
103
conserve space. In projects, instead of duplicating the content of these
103
104
archives, symbolic links are created.
104
105
105
- Simply put, xPacks can be used to further automate the installation of source
106
- libraries and tools.
106
+ Simply put, xpm packages can be used to further automate the
107
+ installation of source libraries and tools.
107
108
108
109
</details >
109
110
0 commit comments