guix/documentation-manual — Hebrew @ Fedora Weblate: Update the file database.

Translation

Source change

English type: table

Hebrew

Needs editing

Skip

	English	Hebrew	Actions
	$ guix locate -g '*.service' man-db@@2.11.1 @dots{}/lib/systemd/system/man-db.service wpa-supplicant@@2.10 @dots{}/system-services/fi.w1.wpa_supplicant1.service
	The @command{guix locate} command relies on a database that maps file names to package names. By default, it automatically creates that database if it does not exist yet by traversing packages available @emph{locally}, which can take a few minutes (depending on the size of your store and the speed of your storage device).
	For now, @command{guix locate} builds its database based on purely local knowledge---meaning that you will not find packages that never reached your store. Eventually it will support downloading a pre-built database so you can potentially find more packages.
	By default, @command{guix locate} first tries to look for a system-wide database, usually under @file{/var/cache/guix/locate}; if it does not exist or is too old, it falls back to the per-user database, by default under @file{~/.cache/guix/locate}. On a multi-user system, administrators may want to periodically update the system-wide database so that all users can benefit from it, for instance by setting up @code{package-database-service-type} (@pxref{File Search Services, @code{package-database-service-type}}).
	The general syntax is:
	guix locate [@var{options}@dots{}] @var{file}@dots{}
	... where @var{file} is the name of a file to search for (specifically, the ``base name'' of the file: files whose parent directories are called @var{file} are not matched).
	The available options are as follows:
	--glob
	-g
	Interpret @var{file}@dots{} as @dfn{glob patterns}---patterns that may include wildcards, such as @samp{*.scm} to denote all files ending in @samp{.scm}.
	--stats
	Display database statistics.
	--update
	-u
	Update the file database.	עדכון חבילת Guix
	By default, the database is automatically updated when it is too old.
	--clear
	Clear the database and re-populate it.
	This option lets you start anew, ensuring old data is removed from the database, which also avoids having an endlessly growing database. By default @command{guix locate} automatically does that periodically, though infrequently.
	--database=@var{file}
	Use @var{file} as the database, creating it if necessary.
	By default, @command{guix locate} picks the database under @file{~/.cache/guix} or @file{/var/cache/guix}, whichever is the most recent one.
	--method=@var{method}
	-m @var{method}
	Use @var{method} to select the set of packages to index. Possible values are:
	manifests
	This is the default method: it works by traversing profiles on the machine and recording packages it encounters---packages you or other users of the machine installed, directly or indirectly. It is fast but it can miss other packages available in the store but not referred to by any profile.
	This is a slower but more exhaustive method: it checks among all the existing packages those that are available in the store and records them.
	Invoking @command{guix gc}
	garbage collector

Loading…

None

String updated in the repository

English

Hebrew 16 characters edited Current translation Needs editing

10 months ago

None

Source string changed

English 13 characters edited

10 months ago

Browse all string changes

Things to check

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Glossary

English	Hebrew
No related strings found in the glossary.

String information

Source string description

type: table

Source string location

guix-git/doc/guix.texi:4093

String age

10 months ago

Last updated

8 days ago

Source string age

10 months ago

Translation file

po/doc/guix-manual.he.po, string 2189