28 lines
1010 B
Markdown
28 lines
1010 B
Markdown
|
## Advantages
|
||
|
|
|
||
|
|
> ### Cross libc
|
||
|
|
> +0-15% performance, depending on the application
|
||
|
|
> packages use the most appropriate libc library
|
||
|
|
> ### Profile-guided optimization
|
||
|
|
> +5-20% performance, optimization for any usage scenario
|
||
|
|
> (to use in build set pgo=true in env)
|
||
|
|
|
||
|
|
## Flexibility
|
||
|
|
> ### Simple insulation
|
||
|
|
> At the repository level
|
||
|
|
> Packages with completely incompatible libraries are separated into different repositories:
|
||
|
|
> /pkg/\<repo\>
|
||
|
|
>
|
||
|
|
> Between the packages
|
||
|
|
> Packages are installed as "packages" in different folders:
|
||
|
|
> /pkg/\<repo\>/\<pkgname\>
|
||
|
|
>
|
||
|
|
> The repository combines files /pkg/\<repo\>/\<pkgname\>/{bin, lib, ...} to /pkg/\<repo\>/{bin, lib, ...}
|
||
|
|
> ### Storage optimization
|
||
|
|
> Final Assembly Philosophy:
|
||
|
|
> After the final system build, when no more packages need to be installed.
|
||
|
|
> Flexible removal of all unused files by reading time
|
||
|
|
## Easy to use
|
||
|
|
> Isolating packages makes it easy to find a configuration
|
||
|
|
> `pkg config \<pkgname\>` squirrel makes it even easier
|