docs(server-delivery): model static-link as a blind spot, not a third layer#163
Merged
Conversation
… layer The page listed OS, application, and static-link as three equal layers, but the classification axis was inconsistent: OS and application are "what it belongs to," while static-link is "how it is detected." A statically linked library is part of the application (or an OS package) build, not an independent layer — it is the blind spot that the package manager and the OS package database both miss. Treat the server as two layers (OS, application) and present static-link libraries as a blind spot of both, kept visible (it is the most common rejection cause) but no longer a peer layer. Rename the section accordingly and keep its binary-mode + manual + BDBA guidance.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
서버를 OS·애플리케이션·정적 링크 '세 층'으로 동급 나열했으나 분류 축이 어긋났습니다(OS·앱은 소속 기준, 정적 링크는 탐지 방법 기준). 정적 링크 라이브러리는 독립 층이 아니라 패키지 매니저·OS 패키지 DB가 모두 놓치는 사각지대입니다.
서버를 두 층(OS·애플리케이션)으로 보고, 정적 링크는 '두 층의 사각지대'로 재배치했습니다(가시성은 유지 — 가장 흔한 반려 원인). 섹션 제목을 그에 맞게 바꾸고 바이너리 모드·수기·BDBA 안내는 유지했습니다. 한·영 동일 적용.