diff options
author | Massimiliano Culpo <massimiliano.culpo@gmail.com> | 2023-06-13 11:07:12 +0200 |
---|---|---|
committer | Todd Gamblin <tgamblin@llnl.gov> | 2023-08-15 15:54:37 -0700 |
commit | 6ad0dc3722c778afda37bcab8397ca6e703b5ee9 (patch) | |
tree | b72cc364a5a8bfa241f66d909df87df6b4f22809 /SECURITY.md | |
parent | 87d4bdaa025b624d3b891f4e2f0c4034b502496b (diff) | |
download | spack-6ad0dc3722c778afda37bcab8397ca6e703b5ee9.tar.gz spack-6ad0dc3722c778afda37bcab8397ca6e703b5ee9.tar.bz2 spack-6ad0dc3722c778afda37bcab8397ca6e703b5ee9.tar.xz spack-6ad0dc3722c778afda37bcab8397ca6e703b5ee9.zip |
Transform many package related facts to use a nested function
Each fact that is deduced from package rules, and start with
a bare package atom, is transformed into a "facts" atom containing
a nested function.
For instance we transformed
version_declared(Package, ...) -> facts(Package, version_declared(...))
This allows us to clearly mark facts that represent a rule on the package,
and will be of help later when we'll have to distinguish the cases where
the atom "Package" is being used referred to package rules and not to a
node in the DAG.
Diffstat (limited to 'SECURITY.md')
0 files changed, 0 insertions, 0 deletions