tizen-install-rootstrap
Install custom rootstrap, rootstrap install, 루트스트랩 설치, custom rootstrap installation. Use this skill to install a custom rootstrap package from a ZIP file into the Tizen SDK.
Samsung Electronics · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Samsung/tizen-agent-skills --skill tizen-install-rootstrap技能说明
name: tizen-install-rootstrap description: Install custom rootstrap, rootstrap install, 루트스트랩 설치, custom rootstrap installation. Use this skill to install a custom rootstrap package from a ZIP file into the Tizen SDK. metadata: author: Samsung Electronics last-updated: "2026-08-21" keywords: - rootstrap install - custom rootstrap - 루트스트랩 설치 - rootstrap package - cross-compilation - toolchain
Claude Code (서브에이전트 위임)
Agent tool 이 없으면 (예: Cline) 아래 "CLI Runner" 섹션으로 가세요.
- Agent tool 로
tizen-install-rootstrap에이전트 호출 - 수집된 입력 (zipPath, force 옵션) 을 프롬프트로 전달
- 서브에이전트의 JSON Envelope를 그대로 사용자에게 전달 — 아래 "결과 보고" 규칙을 따른다
(fenced
json블록으로 원문을 싣고, 그 아래 요약은 1~2줄만)
Prerequisite: Tizen SDK must be installed
Custom rootstrap packages are SDK extension packages, so Tizen SDK must be installed first.
- Tizen SDK installed → Proceed with rootstrap installation
- Tizen SDK NOT installed → Abort with error: "Tizen SDK 가 먼저 설치되어야 합니다. tizen-sdk-install 스킬을 사용하여 SDK 를 설치하세요."
installRootstrap() Flow
1. Validate ZIP file path (security checks) ← path traversal, symlinks rejected
2. Verify Tizen SDK is installed (sdk.info) ← abort if not found
3. Check .rootstrap-installed marker ← present and no --force: success envelope from the marker, stop here
4. Extract ZIP to temporary directory
5. Detect ZIP structure (data/ or tizen-studio/)
6. Parse rootstrap XML metadata from plugins directory
7. Copy tools/ folder to SDK
8. Copy platforms/ folder to SDK
9. For tizen-studio structure: check native packages, copy as tizen-7.0
10. Create .rootstrap-installed marker on success
What the installer does
-
Validates ZIP path for security:
- Decodes URL-encoded sequences (prevent bypass attempts)
- Rejects path traversal (
..) - Normalizes Windows separators
- Verifies
.zipextension - Checks file existence
-
Extracts ZIP to temporary directory:
- Location:
{SDK_TOOLS_PATH}/server/sdktools/rootstrap/extract-* - Validates each ZIP entry for path traversal
- Rejects encrypted entries and symlinks
- Location:
-
Detects ZIP structure:
data/layout: Standard rootstrap packagetizen-studio/layout: Requires native development packages
-
Parses rootstrap XML metadata (
tools/smart-build-interface/plugins/*.core*.xml). Two filename formats are accepted:{profile}-{version}-{device}.core.xml— the Tizen SDK repository format, e.g.tizen-10.0-device.core.xml(packages such astizen-10.0-rs-device.core_<build>_ubuntu-64.zip){profile}-{version}-{device}.core.{public|private}.{timestamp}.xml— custom builds that tag type and build time, e.g.tizen-9.0-arm.core.public.20260819_095020.xml- Extracts: profile, version, device; type and timestamp when present (informational only — the rootstrap identity is
{profile}-{version}-{device})
-
Copies folders:
tools/→{SDK_PATH}/tools/platforms/→{SDK_PATH}/platforms/
-
Special handling for tizen-studio structure:
- Checks for native development package
- Copies platform as
tizen-7.0for compatibility
-
Creates marker file:
.rootstrap-installedwith installation details
Supported ZIP Structures
Structure 1: data/ Layout
rootstrap.zip
└── data/
├── tools/
│ └── smart-build-interface/
│ └── plugins/
│ └── {profile}-{version}-{device}.core[.{public|private}.{timestamp}].xml
└── platforms/
└── tizen-{version}/
└── tizen/
└── rootstraps/
└── {profile}-{version}-{device}.core[.{public|private}.{timestamp}]/
Structure 2: tizen-studio/ Layout
rootstrap.zip
└── tizen-studio/
├── tools/
│ └── smart-build-interface/
│ └── plugins/
│ └── {profile}-{version}-{device}.core[.{public|private}.{timestamp}].xml
└── platforms/
└── tizen-{version}/
└── tizen/
└── rootstraps/
└── {profile}-{version}-{device}.core[.{public|private}.{timestamp}]/
CLI Runner (Cline / Claude Code — Phase 1: Pre-check)
This CLI is a pre-check, not the installer. It finishes in seconds. Run in foreground — NEVER with run_in_background: true.
Pick the ONE block for the shell your terminal / tool runs — the prompt tells you: $ is Bash (Linux, macOS, Claude Code's Git Bash on Windows, Codex on Linux / macOS) → Bash block; PS C:\…> is PowerShell (Codex on Windows, Cline PowerShell terminal) → PowerShell block; C:\…> is cmd.exe (Cline cmd.exe terminal) → cmd.exe block. Run that block as-is: a block pasted into another shell, or wrapped in powershell -Command "…", is a parse error.
Run the node line exactly as written and read the JSON envelope it prints to stdout. Do NOT redirect or capture the output (> file, 2>&1 | tee, Out-File, | Out-String), do NOT wrap the line in cmd /c, powershell -Command "…" or any second shell, and do NOT mix shell dialects: %TEMP% and 2>nul are cmd.exe only, $env:TEMP and Out-File are PowerShell only — in the other shell they are literal text or a parse error. A tool message that the command's completion or output "could not be observed / captured" means the terminal is still busy with an earlier command or its shell-integration hooks have broken, not that the runner failed: open a NEW terminal and re-run the SAME line unchanged. Runners that drive em-cli, sdb or a JVM can take 10–30 s and print the envelope only when they exit — wait for it rather than retrying with a redirect.
Bash — Linux / macOS / Ubuntu, and Windows Git Bash (Claude Code):
BASE="$HOME/.cline"; [ -z "${CODEX_THREAD_ID:-}${CODEX_SANDBOX_NETWORK_DISABLED:-}${CODEX_SANDBOX:-}${CODEX_VERSION:-}" ] || BASE="$HOME/.codex"; [ -z "${GEMINI_CLI:-}" ] || BASE="$HOME/.gemini"; [ -z "${CLAUDECODE:-}" ] || BASE="$HOME/.claude"
_tz_o=; [ -z "${ZSH_
阅读完整来源 ↗