Alpine Linux Install Package Code Example


Example 1: apk add

apk-tools 2.8.2, compiled for x86_64.  usage: apk COMMAND [-h|--help] [-p|--root DIR] [-X|--repository REPO] [-q|--quiet] [-v|--verbose] [-i|--interactive] [-V|--version] [-f|--force]            [--force-binary-stdout] [--force-broken-world] [--force-non-repository] [--force-old-apk] [--force-overwrite] [--force-refresh] [-U|--update-cache]            [--progress] [--progress-fd FD] [--no-progress] [--purge] [--allow-untrusted] [--wait TIME] [--keys-dir KEYSDIR] [--repositories-file REPOFILE]            [--no-network] [--no-cache] [--cache-dir CACHEDIR] [--arch ARCH] [--print-arch] [ARGS]...  The following commands are available:   add       Add PACKAGEs to 'world' and install (or upgrade) them, while ensuring that all dependencies are met   del       Remove PACKAGEs from 'world' and uninstall them   fix       Repair package or upgrade it without modifying main dependencies   update    Update repository indexes from all remote repositories   info      Give detailed information about PACKAGEs or repositories   search    Search package by PATTERNs or by indexed dependencies   upgrade   Upgrade currently installed packages to match repositories   cache     Download missing PACKAGEs to cache and/or delete unneeded files from cache   version   Compare package versions (in installed database vs. available) or do tests on literal version strings   index     Create repository index file from FILEs   fetch     Download PACKAGEs from global repositories to a local directory   audit     Audit the directories for changes   verify    Verify package integrity and signature   dot       Generate graphviz graphs   policy    Show repository policy for packages   stats     Show statistics about repositories and installations   manifest  Show checksums of package contents  Global options:   -h, --help              Show generic help or applet specific help   -p, --root DIR          Install packages to DIR   -X, --repository REPO   Use packages from REPO   -q, --quiet             Print less information   -v, --verbose           Print more information (can be doubled)   -i, --interactive       Ask confirmation for certain operations   -V, --version           Print program version and exit   -f, --force             Enable selected --force-* (deprecated)   --force-binary-stdout   Continue even if binary data is to be output   --force-broken-world    Continue even if 'world' cannot be satisfied   --force-non-repository  Continue even if packages may be lost on reboot   --force-old-apk         Continue even if packages use unsupported features   --force-overwrite       Overwrite files in other packages   --force-refresh         Do not use cached files (local or from proxy)   -U, --update-cache      Update the repository cache   --progress              Show a progress bar   --progress-fd FD        Write progress to fd   --no-progress           Disable progress bar even for TTYs   --purge                 Delete also modified configuration files (pkg removal) and uninstalled packages from cache (cache clean)   --allow-untrusted       Install packages with untrusted signature or no signature   --wait TIME             Wait for TIME seconds to get an exclusive repository lock before failing   --keys-dir KEYSDIR      Override directory of trusted keys   --repositories-file REPOFILE Override repositories file   --no-network            Do not use network (cache is still used)   --no-cache              Do not use any local cache path   --cache-dir CACHEDIR    Override cache directory   --arch ARCH             Use architecture with --root   --print-arch            Print default arch and exit

Example 2: alpine.js install

<script src="https://cdn.jsdelivr.net/gh/alpinejs/alpine@v2.x.x/dist/alpine.min.js" defer></script>

Comments

Post a Comment

Popular posts from this blog

Are Regular VACUUM ANALYZE Still Recommended Under 9.1?

Answer : VACUUM is only needed on updated or deleted rows in non-temporary tables. Obviously you're doing lots of INSERTs but it's not obvious from the description that you're also doing lots of UPDATEs or DELETEs. These operations can be tracked with the pg_stat_all_tables view, specifically the n_tup_upd and n_tup_del columns. Also, even more to the point, there is a n_dead_tup column that tells, per table, how much rows need to be vacuumed. (see Monitoring statistics in the doc for functions and views related to statistics gathering). A possible strategy in your case would be to suppress the scheduled VACUUM, keeping an eye on this view and checking on which tables the n_dead_tup is going up significantly. Then apply the aggressive VACUUM to these tables only. This will be a win if there are large tables whose rows never get deleted nor updated and the aggressive VACUUM is really necessary only on smaller tables. But keep running the ANALYZE for the optimiz
Read more

Can Feynman Diagrams Be Used To Represent Any Perturbation Theory?

Answer : Diagram machinery works also for perturbation theory in classical statistical mechanics and classical field theories. Generally, various kinds of diagrams constitute a pictorial way of talking about tensor products and their contractions while hiding the multi-linear algebra from the layman. In the simplest case, vertices (or blobs) represent vectors, matrices, tensors; vertices have ingoing and/or outgoing ports; ingoing ports denote (contravariant) ro indices; outgoing ports denote (covariant) co indices; directed arcs between blobs give a pair of equal indices summed over; different base spaces ⇔ \Leftrightarrow ⇔ different arc types; symmetric tensors ⇔ \Leftrightarrow ⇔ undirected diagrams; no labels are needed for internal lines. In many cases, the directed arcs are decorated (as thin, thick, broken,wavy, curly lines), each decoration indicating the presence of a so-called propagator, a function of its label to use as a weight in the sum, which may beco
Read more