Update PACKAGE and PACK documentation
@@ -1946,8 +1946,11 @@ PACKED_PACKAGE_ARGS=
PACKED_PACKAGE_EXT=
### @usage: PACK(archive_type)
###
-### When placed inside the PACKAGE module, packs the build results tree to the archive with specified extension.
-### Is not allowed in other module types.
+### When placed inside the PACKAGE module, packs the build results tree to the archive with specified extension. Currently supported extensions are `tar` and `tar.gz`
+###
+### Is not allowed other module types than PACKAGE().
+###
+### @see: [PACKAGE()](#module_PACKAGE)
macro PACK(Ext) {
SET(PACKED_PACKAGE_EXT $Ext)
}
@@ -1961,10 +1964,13 @@ macro PACKAGE_STRICT() {
###
### Module collects what is described directly inside it, builds and collects all its transitively available PEERDIRs.
### As a result, build directory of the project gets the structure of the accessible part of Arcadia, where the build result of each PEERDIR is placed to relevant Arcadia subpath.
+### The data can be optionally packed if macro PACK() is used.
###
### Is only used together with the macros FILES(), PEERDIR(), COPY(), FROM_SANDBOX(), RUN_PROGRAM or BUNDLE(). Don't use SRCS inside a PACKAGE.
###
### Documentation: https://wiki.yandex-team.ru/yatool/large-data/
+###
+### @see: [PACK()](#macro_PACK)
module PACKAGE: _BASE_UNIT {
.CMD=TOUCH_PACKAGE_MF
.PEERDIR_POLICY=as_build_from
