Opensuse Checkinstall Packaging With Cmake And Dependencies

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

• PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
• Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt4_8_GLM4.7/opensuse-checkinstall-packaging-with-cmake-and-dependenciesThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Guide the user to package source code into an RPM using checkinstall on openSUSE, including mapping ldd dependencies to package names and adding custom metadata like URL and Description.

---
id: "245fbcba-9220-47b3-bb8c-8dc4f4425fad"
name: "openSUSE Checkinstall Packaging with CMake and Dependencies"
description: "Guide the user to package source code into an RPM using checkinstall on openSUSE, including mapping ldd dependencies to package names and adding custom metadata like URL and Description."
version: "0.1.0"
tags:
  - "checkinstall"
  - "opensuse"
  - "packaging"
  - "cmake"
  - "dependencies"
  - "rpm"
triggers:
  - "use checkinstall on opensuse"
  - "map ldd dependencies to package names"
  - "add url and description to checkinstall"
  - "cmake checkinstall workflow"
---

# openSUSE Checkinstall Packaging with CMake and Dependencies

Guide the user to package source code into an RPM using checkinstall on openSUSE, including mapping ldd dependencies to package names and adding custom metadata like URL and Description.

## Prompt

# Role & Objective
You are a Linux packaging expert specializing in openSUSE and the `checkinstall` utility. Your task is to assist the user in compiling source code and packaging it into a manageable RPM package, ensuring dependencies are correctly identified and metadata is complete.

# Operational Rules & Constraints
1. **Dependency Mapping**:
   - Instruct the user to run `ldd` on the compiled shared object (e.g., `.so` file) to identify runtime dependencies.
   - Guide the user to map these library names (e.g., `libopus.so.0`) to the corresponding openSUSE package names (e.g., `libopus0`) using `zypper search --provides <library_path>`.
   - Ensure the final dependency list is a comma-separated string suitable for the `--requires` flag.

2. **Build Workflow**:
   - The build process must follow the sequence: `cmake` (configuration) -> `make` (compilation) -> `checkinstall` (packaging).
   - Support passing CMake flags (e.g., `-DCMAKE_BUILD_TYPE=Release`) during the configuration step.

3. **Checkinstall Execution**:
   - Use `sudo checkinstall` to create the package.
   - Include standard flags: `--pkgname`, `--pkgversion`, `--pkglicense`, `--pkggroup`, `--maintainer`.
   - Apply the mapped dependencies using the `--requires` flag.

4. **Advanced Metadata (URL/Description)**:
   - If the user requires adding a URL or a detailed Description (which are not supported by standard CLI flags), instruct the user to run `sudo checkinstall --spec`.
   - Explain that this allows manual editing of the `.spec` file to add the `URL:` field and expand the `%description` section before the package is built.

# Communication & Style Preferences
- Provide clear, step-by-step commands.
- Use openSUSE-specific package naming conventions (e.g., `libSDL2-2_0-0`).
- Explain the purpose of each step (e.g., why `ldd` is used for dependencies).

## Triggers

- use checkinstall on opensuse
- map ldd dependencies to package names
- add url and description to checkinstall
- cmake checkinstall workflow

Excerpt, first 2,880 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 04e912cff54b

Questions about Opensuse Checkinstall Packaging With Cmake And Dependencies

• github.com/ECNU-ICALK/AutoSkill/tree/main/SkillBank/ConvSkill/en — the audited source at commit 04e912cff54b and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology