facebook/buck2：README 來源編輯指南

facebook/buck2 的 README 將專案描述為「Build system, successor to Buck」。本文只整理倉庫可直接核對的內容，不把 star、Fork 或宣傳語當成品質證明。README 在「Buck2: fast multi-language build system」下寫到：Buck2 is a fast, hermetic, multi-language build system, and a direct successor to the original Buck build system — both designed by Meta.。這說明的是專案邊界，不是已完成的生產驗證。

從 README 的「Buck2: fast multi-language build system」與相關條目，可以先判斷它是否處理你的實際問題：Hermetic. When using Remote Execution[^hermetic-re-only], Buck2 becomes。若需求不同，不應只因專案熱度就採用。本文保留原始專案名、命令與元件名，方便回到一手來源核對。 README 另外列出一項可核對的資訊：Fast. It doesn't matter whether a single build command takes 60 seconds to。這類原文條目可用來設計試跑步驟，但不能取代實際環境測試。

README 將運作方式分散在「Buck2: fast multi-language build system」等段落。可確認的線索包括：complete, or 0.1 seconds: when you have to build things, Buck2 doesn't waste time — it calculates the critical path and gets out of the way, with minimal overhead.。本文不把未寫出的架構、效能或安全邊界補成結論；真正的執行鏈仍要配合目錄、設定檔與版本標籤檢查。

第一次安裝應從 README 指出的入口開始。目前可核對的命令是： README 没有给出可直接复制的安装命令。 如果倉庫沒有命令，本文不會自行編造步驟，而是建議先閱讀「🚧🚧🚧 Warning 🚧🚧🚧 — rough terrain lies ahead」，確認系統依賴、預設埠與首次初始化。

日常使用取決於專案文件。README 的「Buck2: fast multi-language build system」段落提到：hermetic: it is required for a build rule to correctly declare all of its inputs; if they aren't specified correctly (e.g. a .c file needs a .h file that isn't correctly specified), the build will fail.。設定檔、環境變數、權限與資料目錄只在來源明確時才會記錄；沒有寫出的預設值，應在測試環境驗證並保留回滾副本。 同一部分也提到：Multi-language. Many teams have to deal with multiple programming。

README 能確認的限制比宣傳頁更重要。現有來源沒有證明facebook/buck2具備固定相容矩陣、服務等級、效能基準或長期支援承諾。README 只明確寫到「languages that have complex inter-dependencies, and struggle to express that. Most people settle with make and tie together dune to pip and cargo. But then how do you run test suites, code coverage, or query code databases?」。這些未知項應列入選型紀錄，不要改成肯定句。