CHICKEN-INSTALL(1)
π CHICKEN-INSTALL π
okay so bestie, this is a page from the General Commands Manual β it's chicken-install(1), and honestly? she's that girl. buckle up π
β¨ SYNOPSIS β¨
chicken-install [OPTION ...] [NAME[:VERSION] ...]
πΈ DESCRIPTION πΈ
chicken-install downloads, compiles and installs a prepackaged extension library from sources. literally the whole glow-up pipeline in one command π
and listen β if no extension name is given on the command line, then any existing egg descriptions in the current directory will be executed in unspecified order. no cap, unspecified. don't come for me about ordering, it's giving chaos-on-purpose π
the program accepts the following arguments:
π¦ the arguments (yes, all of them, i'm not skipping a single one) π¦
-h,-helpβ show usage and exit. bye bestie π-versionβ show version and exit.-v,-verboseβ print extra information during installation. she's chatty and we love that π£οΈ-forceβ install without confirmation, even if versions don't match. bold. reckless. iconic π₯-k,-keepβ keep temporary files. packrat energy πΏοΈ-s,-sudoβ use an external program to elevate privileges for filesystem operations. the program defaults tosudo(8)but can be overridden with theSUDOenvironment variable. so fancy π-r,-retrieveβ just retrieve the egg, don't install it. (giving-rmore than once implies-recursive.) window shopping only ποΈ-recursiveβ if-retrieveis given, also fetch dependencies recursively. it's giving "and bring your friends" π«Ά-dry-runβ do not build or install, just print the locations of the generated build & install scripts. rehearsal, not the actual show π-list-versionsβ list available versions for the given eggs. the whole menu π-purgeβ remove cached files for given eggs (or purge cache completely). spring cleaning, but make it filesystem π§Ή-hostβ when cross-compiling, only compile extensions for host.-targetβ when cross-compiling, only compile extensions for target.-testβ run included test cases, if available. vibe check β-n,-no-installβ do not install the egg, just build it. built different, installed never ποΈ-no-install-dependenciesβ do not install dependencies. > note: this option may result in build failures due to missing extension libraries. so like... you were warned, bestie π-u,-update-dbβ update export database.-repositoryβ print path used for egg installation.-overridefilename β override versions for installed eggs with information from filename.-from-listfilename β install eggs listed in filename, which has the same format aschicken-status(1)'s-listoutput. this option may be given multiple times. love a repeatable queen π-cachedβ only install eggs from cache, do not download. no new tabs, only the ones already open π-l,-locationdirectory β get egg sources from the given directory. may be provided multiple times. locations specified on the command line have precedence over the ones specified insetup.defaultsποΈ-feature,-Dname β register feature name, usable as a condition incond-expandclauses. so conditional, so slay β¨
π§ ENVIRONMENT π§
following environment variables change the behaviour of chicken-install:
CHICKEN_EGG_CACHEβ location where eggs are retrieved and built.CHICKEN_INSTALL_PREFIXβ the path prefix for all target files, as given when building the system. use this variable to override where programs, include files and additional data files shall be installed.CHICKEN_INSTALL_REPOSITORYβ the path where extension libraries are installed. defaults to the package library path selected during configuration (usually$prefix/lib/chicken/<binary-version>). > note that this variable takes precedence toCHICKEN_INSTALL_PREFIX. she said "i'm the main character here" πSUDOβ the command to execute when using-sflag in command. if not provided, defaults tosudo(8).
π FILES π
$XDG_CONFIG_HOME/chicken/setup.defaultsβ user specificsetup.defaultsfile. ($XDG_CONFIG_HOMEdefaults to$HOME/.config)$prefix/share/chicken/setup.defaultβ system-widesetup.defaultsfile.$XDG_CACHE_HOME/chicken-install/β default directory for cached eggs. ($XDG_CACHE_HOMEdefaults to$HOME/.cache)
β EXIT STATUS β
the chicken-install utility exits 0 on success, 2 if the user aborted an operation, 3 if it was invoked with no explicitly given egg names and no *.egg files could be found in the current directory, and >0 if any other error occurs. read the numbers, know the numbers π’β¨
π EXAMPLES π
install 'regex' egg as root user:
# chicken-install regex
install an egg as an normal user but using sudo(8):
$ chicken-install -s regex
install an egg as an normal user but elevating privileges with different program, such as OpenBSD doas(1):
$ SUDO=/usr/bin/doas chicken-install -s regex
see? different program, same slay π
π«Ά SEE ALSO π«Ά
chicken(1), chicken-status(1), chicken-uninstall(1), csc(1)
more information can be found in the CHICKEN User's Manual: http://wiki.call-cc.org/manual/index. iykyk π
π AUTHORS π
the CHICKEN Team. collectively iconic, no notes. ππ
π BUGS π
submit bug reports by e-mail to chicken-janitors@nongnu.org. do it, they're nice, and honestly they want to hear from you π
and that's the page bestie!! this version came to you courtesy of Debian, dated Apr 26, 2017 β yes that's the date, no that's not a typo, we're just built different πΈπ¦ periodt.
π¦ where this page comes from
- arch rolling: chicken 6.0.0-1 Β· BSD-3-Clause AND GPL-2.0-or-later AND custom:Public-Domain
- nixpkgs unstable: chicken 6.0.0
- Copyright (c) 2007-2022, The CHICKEN Team
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms