Salt 3000 requires setuptools to build. Older distributions don't provide that.

Salt is a distributed remote execution system used to execute commands and
query data. It was developed in order to bring the best solutions found in
the world of remote execution together and make them better, faster and more
malleable. Salt accomplishes this via its ability to handle larger loads of
information, and not just dozens, but hundreds or even thousands of individual
servers, handle them quickly and through a simple and manageable interface.

Salt is a distributed remote execution system used to execute commands and
query data. It was developed in order to bring the best solutions found in
the world of remote execution together and make them better, faster and more
malleable. Salt accomplishes this via its ability to handle larger loads of
information, and not just dozens, but hundreds or even thousands of individual
servers, handle them quickly and through a simple and manageable interface.

https://src.opensuse.org/salt/

Devel project for Uyuni/MLM AI artifacts

## Snapshot Dependency Strategy for Building
This strategy resolves the conflict between the continuous churn of upstream repositories (e.g., devel:languages:python) and the stability required for our internal tooling and projects by creating a frozen, snapshot-based build environment.

### How It Works
* RPM Only: All components and dependencies are built and delivered strictly as RPM packages.

* Snapshot Copies (No Links): To avoid "moving targets" and desynchronization, dependencies must be explicitly copied as snapshots rather than linked.

* Source Suffix Tracking: Copied packages use a suffix to identify their origin. For example, .dlp indicates the package was snapshot-copied from devel:languages:python.

* Sources for packages: first look for packages in devel projects, i.e `devel:languages:python` and its subprojects. (Note home:pluskalm:fastmcp is "staging" for the fastmcp packages before they are updated into `devel:languages:python`.)

* Workflow:
* Use copypac -e to copy existing upstream source and spec files into this project (remembering to add the suffix).

* Brand-new packages should be built directly within this project with py2pack (use latest version from tumbleweed)

* You might need some python build dependencies like python-trove-classifiers . These are dependencies that are used to check the python artifacts. Because the packages have been generated with the latest py2pack (from tumbleweed), you also need to copy these dependencies. You can copy them from `d:l:p` . If a dependency is missing, you will see a failure in the build of the package, usually pointing to some wrong metadata (which actually means wrong version of the checker, i.e. trove-classifiers).

## Legal Disclaimer and Status (Tech Preview)
All artifacts are provided strictly for prototyping, development, and feedback. They are officially designated as a Technology Preview.

These artifacts are explicitly UNSUPPORTED, unmaintained, and come with NO WARRANTY of any kind.

## Usage Restriction
Do not deploy or use these artifacts in production environments, mission-critical systems, or any scenario where a failure could result in damages or data loss. Users accept all risks.