XPack Component Interfaces
set_title
- Set a brief description of the package components
Function Prototype
API
set_title(title: <string>)Parameter Description
| Parameter | Description |
|---|---|
| title | Component title string |
Usage
xpack_component("LongPath")
set_title("Enable Long Path")set_description
- Set detailed description of package components
Function Prototype
API
set_description(description: <string>)Parameter Description
| Parameter | Description |
|---|---|
| description | Component description string |
Usage
xpack_component("LongPath")
set_description("Increases the maximum path length limit, up to 32,767 characters (before 256).")set_default
- Set the default enabled state of package components
Function Prototype
API
set_default(default: <boolean>)Parameter Description
| Parameter | Description |
|---|---|
| default | Whether component is enabled by default (boolean) |
Usage
Usually the package component is enabled by default, but we can also use this interface to disable this component by default. Only when the user chooses to check this component when installing the package will it be enabled for installation.
xpack_component("LongPath")
set_default(false)
set_title("Enable Long Path")on_load
- Custom loading script
Function Prototype
API
on_load(script: <function (component)>)Parameter Description
| Parameter | Description |
|---|---|
| script | Load script function with component parameter |
Usage
We can further flexibly configure package components in the on_load custom script field.
xpack_component("test")
on_load(function (component)
local package = component:package()
-- TODO
end)before_installcmd
- Add script before component installation
Function Prototype
API
before_installcmd(script: <function (component, batchcmds)>)Parameter Description
| Parameter | Description |
|---|---|
| script | Before install script function with component and batchcmds parameters |
Usage
It will not rewrite the entire installation script, but will add some custom installation scripts before the existing installation scripts are executed:
xpack_component("test")
before_installcmd(function (component, batchcmds)
batchcmds:mkdir(package:installdir("resources"))
batchcmds:cp("src/assets/*.txt", package:installdir("resources"), {rootdir = "src"})
batchcmds:mkdir(package:installdir("stub"))
end)It should be noted that the cp, mkdir and other commands added through batchcmds will not be executed immediately, but will only generate a command list. When the package is actually generated later, these commands will be translated into packaging commands.
It is exactly the same as xpack's before_installcmd. The only difference is that the installation script here will only be executed when this component is enabled.
on_installcmd
- Rewrite the installation script of the component
Function Prototype
API
on_installcmd(script: <function (component, batchcmds)>)Parameter Description
| Parameter | Description |
|---|---|
| script | Install script function with component and batchcmds parameters |
Usage
Custom installation script for implementing specific component installation logic.
This will rewrite the entire component's installation script, similar to xpack's on_installcmd.
xpack_component("test")
on_installcmd(function (component, batchcmds)
-- TODO
end)after_installcmd
- Add script after component installation
Function Prototype
API
after_installcmd(script: <function (component, batchcmds)>)Parameter Description
| Parameter | Description |
|---|---|
| script | After install script function with component and batchcmds parameters |
Usage
Custom script executed after component installation, used for post-processing operations.
After the component is installed, the script here will be executed, similar to xpack's after_installcmd.
xpack_component("test")
after_installcmd(function (component, batchcmds)
-- TODO
end)before_uninstallcmd
- Add script before component uninstallation
Function Prototype
API
before_uninstallcmd(script: <function (component, batchcmds)>)Parameter Description
| Parameter | Description |
|---|---|
| script | Before uninstall script function with component and batchcmds parameters |
After the component is installed, the script here will be executed, similar to xpack's before_uninstallcmd.
xpack_component("test")
before_uninstallcmd(function (component, batchcmds)
-- TODO
end)on_uninstallcmd
- Rewrite the script for component uninstallation
Function Prototype
API
on_uninstallcmd(script: <function (component, batchcmds)>)Parameter Description
| Parameter | Description |
|---|---|
| script | Uninstall script function with component and batchcmds parameters |
Usage
Custom uninstall script for implementing specific component uninstall logic.
This will rewrite the entire component's uninstall script, similar to xpack's on_uninstallcmd.
xpack_component("test")
on_uninstallcmd(function (component, batchcmds)
-- TODO
end)after_uninstallcmd
- Add script after component uninstallation
Function Prototype
API
after_uninstallcmd(script: <function (component, batchcmds)>)Parameter Description
| Parameter | Description |
|---|---|
| script | After uninstall script function with component and batchcmds parameters |
Usage
Custom script executed after component uninstallation, used for post-processing operations.
After the component is uninstalled, the script here will be executed, similar to xpack's before_uninstallcmd.
xpack_component("test")
before_uninstallcmd(function (component, batchcmds)
-- TODO
end)add_sourcefiles
- Add component source file
Function Prototype
API
add_sourcefiles(files: <string|array>, ..., {
prefixdir = <string>,
rootdir = <string>,
filename = <string>
})Parameter Description
| Parameter | Description |
|---|---|
| files | Source file pattern string or array |
| ... | Variable parameters, can pass multiple file patterns |
| prefixdir | Installation prefix directory |
| rootdir | Source root directory |
| filename | Target filename |
This is similar to xpack's add_sourcefiles, but here only when the component is enabled, these source files will be added to the installation package.
add_installfiles
- Add component binary installation file
Function Prototype
API
add_installfiles(files: <string|array>, ..., {
prefixdir = <string>,
rootdir = <string>,
filename = <string>
})Parameter Description
| Parameter | Description |
|---|---|
| files | Install file pattern string or array |
| ... | Variable parameters, can pass multiple file patterns |
| prefixdir | Installation prefix directory |
| rootdir | Source root directory |
| filename | Target filename |
Usage
This is similar to xpack's add_installfiles, but here only the binaries are added to the installation package when the component is enabled.