> For the complete documentation index, see [llms.txt](https://book.bsdcn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.bsdcn.org/porters-handbook/di-7-zhang-flavors/7.5.useslua-he-flavors.md).

# 7.5.USES=lua 和 Flavors

当使用 [`lua:module`](https://docs.freebsd.org/en/books/porters-handbook/uses/#uses-lua) 或 [`lua:flavors`](https://docs.freebsd.org/en/books/porters-handbook/uses/#uses-lua) 时，Port 会自动填充 `FLAVORS`，其中包含它所支持的 Lua 版本。不过，普通的应用程序（而不是 Lua 模块）通常不应使用这个功能；大多数嵌入或使用 Lua 的应用程序只需简单地使用 `USES=lua`。

`LUA_FLAVOR` 是可用的（并且必须使用）变量，用于依赖正确版本的依赖项，无论该 Port 是否使用了 `flavors` 或 `module` 参数。

有关更多信息，请参见 [使用 Lua](https://docs.freebsd.org/en/books/porters-handbook/special/#using-lua)。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://book.bsdcn.org/porters-handbook/di-7-zhang-flavors/7.5.useslua-he-flavors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.