porting
Skill1 starsChanged 9 months agoMITView on GitHub
Port a package from nixpkgs into corepkgs. Use when adding a package that already exists upstream — covers copying it across, checking dependencies first, stripping nixpkgs-only attributes, recording TODOs for missing features, and wiring it into top-level.nix.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- HypothesisWorks/hypothesistheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- HypothesisWorks/hypothesis★ 9.1ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cmakeSkill
- ekala-cmake-nixSkill
- ekapkgs-repoSkill
- goSkill
- mesonSkill
- mk-many-variantsSkill
- nix-buildSkill
- nix-evalSkill
- packagingSkill
- pythonSkill
- rustSkill
- structured-attrsSkill
- validationSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Do this before importing anything: a package whose dependencies are missing cannot be evaluated, and it is cheaper to find out now than …
- Very specific: line 22
Do not grep top-level.nix to check for a dependency.
- Distinctive: line 26
If a dependency is missing, either port it first or add a TODO and disable the feature that needs it (step 4).
- Distinctive: line 90
Every feature turned off for a missing dependency gets a TODO naming the dependency, so the package can be completed later without …
- Very specific: line 114
Run ./ci/eval.sh before committing to confirm nothing else in the set broke.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Porting from nixpkgs
Workflow
1. Check dependencies exist
Do this before importing anything: a package whose dependencies are missing cannot be evaluated, and it is cheaper to find out now than after editing.
for dep in acl lzo cmocka libuuid util-linux zlib zstd; do
printf '%s: ' "$dep"
nix-instantiate -A "$dep" >/dev/null 2>&1 && echo "✓" || echo "✗"
doneDo not grep top-level.nix to check for a dependency. Packages in pkgs/
and pkgs-many/ are registered automatically and often have no entry there. For
attributes that are not derivations, use nix-instantiate --eval -A <attr>.
If a dependency is missing, either port it first or add a TODO and disable the feature that needs it (step 4).
2. Copy the package across
Copy the whole directory so patch files and other assets come along, then rename the entry point to the corepkgs convention.
# pkgs/by-name/cu/curl -> pkgs/curl
cp -r ../nixpkgs/pkgs/by-name/cu/curl pkgs/curl
mv pkgs/curl/package.nix pkgs/curl/default.nix
# pkgs/development/python-modules/httpx -> python/pkgs/httpx
cp -r ../nixpkgs/pkgs/development/python-modules/httpx python/pkgs/httpx| Source in nixpkgs | Destination |
pkgs/by-name/<xx>/<name> | pkgs/<name> |
pkgs/development/python-modules/<name> | python/pkgs/<name> |
pkgs/development/... (older layout) | pkgs/<name> |
<xx> is the lowercase two-letter prefix of the attribute name, so SDL2_gfx
is found under sd/ and R under r/. Only by-name packages have a
package.nix to rename; the older trees already use default.nix.
Copying makes no edits to the expression itself — every cleanup in step 3 is manual.
Packages with multiple versions belong in pkgs-many/ and need to be
restructured into the default.nix / variants.nix / generic.nix layout
rather than copied — see the mk-many-variants skill.
3. Strip nixpkgs-only attributes
meta = {
# maintainers = ...; DELETE — not a recognised meta key here, fails check-meta
# teams = ...; DELETE — likewise
};
passthru = {
# updateScript = gnome.updateScript { ... }; DELETE
tests = { ... }; # KEEP
};Also drop doCheck = false; if the expression sets it — that is already the
default across the package set. To keep a test suite, move it to
passthru.tests instead:
passthru.tests = {
unittests = runUnitTests finalAttrs.finalPackage;
};Build-system hooks are explicit here, so an imported expression usually needs
one added: cmake.configurePhaseHook, or meson.configurePhaseHook plus
ninja. See the cmake and meson skills.
4. Record what you disabled
Every feature turned off for a missing dependency gets a TODO naming the dependency, so the package can be completed later without re-deriving why:
buildInputs = [
zlib
# TODO(corepkgs): Port openssl for TLS support
# TODO(corepkgs): Port libxml2 for XML processing
];
configureFlags = [
"--without-selinux"
"--without-cap"
];5. Validate
nix-instantiate -A example
nix-build -A example
./result/bin/example --versionRun ./ci/eval.sh before committing to confirm nothing else in the set broke.
See the validation skill for the full procedure and error triage.
6. Add to top-level.nix only if needed
Packages in pkgs/ and pkgs-many/ are auto-registered by directory name. Add
an explicit entry only when the inputs deviate from what the expression
declares, or you need to override arguments or pass extra configuration.
Example: straightforward package
{
lib,
stdenv,
fetchFromGitHub,
meson,
ninja,
pkg-config,
libcap,
libseccomp,
}:
stdenv.mkDerivation (finalAttrs: {
pname = "bubblewrap";
version = "0.8.0";
src = fetchFromGitHub {
owner = "containers";
repo = "bubblewrap";
tag = "v${finalAttrs.version}";
hash = "sha256-...";
};
nativeBuildInputs = [
meson
meson.configurePhaseHook
ninja
pkg-config
];
buildInputs = [
libcap
libseccomp
];
meta = {
description = "Unprivileged sandboxing tool";
homepage = "https://github.com/containers/bubblewrap";
license = lib.licenses.lgpl2Plus;
platforms = lib.platforms.linux;
};
})Example: features disabled for missing dependencies
{
lib,
stdenv,
fetchurl,
pkg-config,
zlib,
bzip2,
file,
lua,
}:
stdenv.mkDerivation (finalAttrs: {
pname = "rpm";
version = "4.18.0";
src = fetchurl {
url = "https://ftp.rpm.org/releases/rpm-4.18.x/rpm-${finalAttrs.version}.tar.bz2";
hash = "sha256-...";
};
nativeBuildInputs = [ pkg-config ];
buildInputs = [
zlib
bzip2
file
lua
# TODO(corepkgs): Port popt for enhanced CLI parsing
# TODO(corepkgs): Port beecrypt for signature verification
];
configureFlags = [
"--without-selinux"
"--without-cap"
];
meta = {
description = "RPM Package Manager";
license = lib.licenses.gpl2Plus;
};
})Common issues
Source path does not exist — the package is not in by-name (copy it by
hand), the name is not the attribute name, or --nixpkgs-root points at the
wrong checkout.
error: attribute 'somelib' missing — a dependency was never ported. Port
it, or drop the argument and disable the feature with a TODO.
configure: error: libfoo is required — the build system wants a dependency
you removed. Disable it explicitly, e.g. configureFlags = [ "--without-foo" ];.
Nothing configures / no Makefile found — the build-system hook was not
carried over. Add cmake.configurePhaseHook or meson.configurePhaseHook.
check-meta rejects the package — meta.maintainers or meta.teams
survived the cleanup.
Checklist
- Dependencies checked with
nix-instantiate -A <dep> - Copied across and
package.nixrenamed todefault.nix meta.maintainers,meta.teams, andupdateScriptremoved- Build-system configure hook added
- Missing dependencies recorded as
TODO(corepkgs)comments - License and any security patches preserved
- Validated per the
validationskill, and./ci/eval.shpasses
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

