2.Pkg
The type of Package or Binary
#Example ONLY
pkg: "Real Name, It will be Installed & Integrated based on this Value"
pkg_id: "Unique Identifier, Based on src_url, used for identifying this .pkg"
pkg_type: "Pkg Format, if empty or nonexistent, Builder reads Magic Bytes to determine format"
pkg_id
is to make it seamless to add multiple binaries from multiple sources for the same pkg
pkg_id
is justsrc_url
withouthttp|https
schema along with some extra paramsExample:
src_url
=
"https://
github.com
/
AppImager
/
example-appimage
" -->github.com
.
AppImager
.
example-appimage
Notice how, all special chars like
/
-->.
andhttp://|https://
was removed Another example, where the repo has multiple appimages:
alpha
--> github.com.AppImager.example-appimage.alpha
latest
--> github.com.AppImager.example-appimage.latest
nightly
--> github.com.AppImager.example-appimage.nightly
stable
--> github.com.AppImager.example-appimage.stable
It's just
$tag
or some other identifier added at last
Dynamic denotes it is a Dynamic Binary pkg_type: "dynamic"
NixAppImage denotes it is a NixAppImage , pkg_type: "nixappimage"
Static denotes it is a Static Binary , pkg_type: "static"
Last updated
Was this helpful?