Enter the query into the form above.
API method:
GET /api/symbols?search=hello&page=1&limit=20
where search is your query, page is a page number and limit is a number of items on a single page. Pagination information (such as a number of pages and etc) is returned
in response headers.
If you'd like to join our channel search send a patch to ~whereiseveryone/toys@lists.sr.ht adding your channel as an entry in channels.scm.
Return #t if DRV is a fixed-output derivation, such as the result of a download with a fixed hash (aka. `fetchurl').
Return the store path of its output OUTPUT. Raise a '&derivation-missing-output-error' condition if OUTPUT is not an output of DRV.
Perform a breadth-first traversal of INPUTS, calling PROC on each input with the current result, starting from SEED. Skip recursion on inputs that match CUT?.
Invalidate internal derivation caches. This is mostly useful for long-running processes that know what they're doing. Use with care!
Build a derivation with the given arguments, and return the resulting <derivation> object. When HASH and HASH-ALGO are given, a fixed-output derivation is created---i.e., one whose result is known in advance, such as a file download. If, in addition, RECURSIVE? is true, then that fixed output may be an executable file or a directory and HASH must be the hash of an archive containing this output.
When REFERENCES-GRAPHS is true, it must be a list of file name/store path pairs. In that case, the reference graph of each store path is exported in the build environment in the corresponding file, in a simple text format.
When ALLOWED-REFERENCES is true, it must be a list of store items or outputs that the derivation's outputs may refer to. Likewise, DISALLOWED-REFERENCES, if true, must be a list of things the outputs may not refer to.
When LEAKED-ENV-VARS is true, it must be a list of strings denoting environment variables that are allowed to "leak" from the daemon's environment to the build environment. This is only applicable to fixed-output derivations--i.e., when HASH is true. The main use is to allow variables such as "http_proxy" to be passed to derivations that download files.
When LOCAL-BUILD? is true, declare that the derivation is not a good candidate for offloading and should rather be built locally. This is the case for small derivations where the costs of data transfers would outweigh the benefits.
When SUBSTITUTABLE? is false, declare that substitutes of the derivation's output should not be used.
PROPERTIES must be an association list describing "properties" of the derivation. It is kept as-is, uninterpreted, in the derivation.
Return a one-argument procedure that, when passed a store file name, returns a 'substitutable?' if it's substitutable and #f otherwise.
The returned procedure knows about all substitutes for all the derivation inputs or derivations listed in INPUTS-OR-DRV, *except* those that are already valid (that is, it won't bother checking whether an item is substitutable if it's already on disk); it also knows about their prerequisites, unless they are themselves substitutable.
Creating a single oracle (thus making a single 'substitutable-path-info' call) and reusing it is much more efficient than calling 'has-substitutes?' or similar repeatedly, because it avoids the costs associated with launching the substituter many times.
Read the derivation from PATH (`/gnu/store/xxx.drv'), and return the list of name/path pairs of its outputs.
Read the derivation from DRV-PORT and return the corresponding <derivation> object. Call READ-DERIVATION-FROM-FILE to read derivations declared as inputs of the derivation being parsed.
Most of the time you'll want to use 'read-derivation-from-file', which caches things as appropriate and is thus more efficient.
Return a <derivation-input> for the OUTPUTS of DRV.
Return the file name of the derivation INPUT refers to.