Co-authored-by: mohan002 <mohbabul@amd.com>

* PDT accepts oneapi as provider of icpc compiler

* Add maintainers section (same as for tau)

* Whitespace formatting fix

* rct: new packages (core packages and some dependencies)

* rct: new packages (core packages and some dependencies)

* radical-entk: updated dependencies (according to comments)

* radical-gtod: updated version name

* radical-pilot: updated dependencies (according to comments)

* radical-saga: updated dependencies (according to comments)

* radical-utils: updated dependencies and set old versions deprecated

* saga-python: removed due to absence of packages (in PyPI, GitHub), this project was replaced by `radical-saga` and corresponding package `py-radical-saga` should be used

* saga-python: rolled back, but with deprecation status

* ntplib: removed maintainer

* pika: removed maintainer

Co-authored-by: Harmen Stoppels <harmenstoppels@gmail.com>

The commands have been deprecated in #7098, and have
been failing with an error message since then.

Cleaning the code since it is unlikely that somebody
is still using them.

Isn't installed on Alpine.

* Fix for building shared lib when enabling ROCm, for STRUMPACK 5.1.1.

* Update patch for shared lib with STRUMPACK 5.1.1 and ROCm, also update FindHIP.cmake

* update patch for shared libs with ROCm

Co-authored-by: Harmen Stoppels <harmenstoppels@gmail.com>

Signed-off-by: Aurelien Bouteiller <bouteill@icl.utk.edu>

Co-authored-by: sbulut <sbulut@3vgeomatics.com>

Co-authored-by: sbulut <sbulut@3vgeomatics.com>

The star was not rendered in the docs.

Transfer protocol in the Aluminum library.  If required the Host
Transfer variant +ht should be explicity set.

Co-authored-by: Harmen Stoppels <harmenstoppels@gmail.com>

Preferred providers had a non-zero weight because in an earlier formulation of the logic program that was needed to prefer external providers over default providers. With the current formulation for externals this is not needed anymore, so we can give a weight of zero to both default choices and providers that are externals. _Using zero ensures that we don't introduce any drift towards having less providers, which was happening when minimizing positive weights_.

Modifications:

- [x] Default weight for providers starts at 0 (instead of 10, needed before to prefer externals)
- [x] Rules to compute the `provider_weight` have been refactored. There are multiple possible weights for a given `Virtual`. Only one gets selected by the solver (the one that minimizes the objective function).
- [x] `provider_weight` are now accounting for each different `Virtual`. Before there was a single weight per provider, even if the package was providing multiple virtuals.

* Give preferred providers a weight of zero

Preferred providers had a non-zero weight because in an earlier
formulation of the logic program that was needed to prefer
external providers over default providers.

With the current formulation for externals this is not needed anymore,
so we can give a weight of zero to default choices. Using zero
ensures that we don't introduce any drift towards having
less providers, which was happening when minimizing positive weights.

* Simplify how we compute weights for providers

Rewrite rules so that specific events (i.e. being
an external) unlock the possibility to use certain
weights. The weight being considered is then selected
by the minimization process to be the one that gives
the best score.

* Allow providers to have different weights for different virtuals

Before this change we didn't differentiate providers based on
the virtual they provide, which meant that packages providing
more than one virtual had nonetheless a single weight.

With this change there will be a weight per virtual.