Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
A
asdf
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Pascal J. Bourguignon
asdf
Commits
afa14d6b
Commit
afa14d6b
authored
15 years ago
by
Francois-Rene Rideau
Browse files
Options
Downloads
Patches
Plain Diff
Manual update
parent
eeb5ae12
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
asdf.texinfo
+16
-4
16 additions, 4 deletions
asdf.texinfo
with
16 additions
and
4 deletions
asdf.texinfo
+
16
−
4
View file @
afa14d6b
...
...
@@ -1494,7 +1494,7 @@ The new component type is used in a @code{defsystem} form in this way:
Configurations specify paths where to find system files.
1- An application may explicitly initialize the source-registry
configuration using the
`
Configuration API
`
_
below,
configuration using the
@xref
{
Configuration API
}
below,
in which case this takes precedence.
It may itself compute this configuration from the command-line,
from a script, from its own configuration file, etc.
...
...
@@ -1524,7 +1524,7 @@ Configurations specify paths where to find system files.
7- The source registry will be configured from a default configuration,
which allows for implementation-specific software to be searched.
(See below
`
Backward Compatibility
`
_
).
(See below
@xref
{
Backward Compatibility
}
).
Each of these configuration is specified as a SEXP
in a trival domain-specific language (defined below).
...
...
@@ -1589,7 +1589,7 @@ DIRECTIVE :=
PATTERN := a string without wildcards, that will be matched exactly
against the name of a any subdirectory in the directory component
of a path. e.g.
``
_
darcs
''
will match #p"/foo/bar/
_
darcs/src/bar.asd"
of a path. e.g.
@code
{
"
_
darcs
"
}
will match
@file
{
#p"/foo/bar/
_
darcs/src/bar.asd"
}
@end example
...
...
@@ -1597,7 +1597,7 @@ PATTERN := a string without wildcards, that will be matched exactly
Configuration directories consist in files each contains
a list of directives without any enclosing @code
{
(:source-registry ...)
}
form.
The files will be sorted by namestring as if by #'string< and
The files will be sorted by namestring as if by
@code
{
#'string<
}
and
the lists of directives of these files with be concatenated in order.
An implicit @code
{
:inherit-configuration
}
will be included
at the end of the list.
...
...
@@ -1606,6 +1606,12 @@ This allows for packaging software that has file granularity
(e.g. Debian's @code
{
dpkg
}
or some future version of @code
{
clbuild
}
)
to easily include configuration information about distributed software.
The convention is that, for sorting purposes,
the names of files in such a directory begin with two digits
that determine the order in which these entries will be read.
Also, the type of these files is conventionally @code
{
"conf"
}
and as a limitation of some implementations, the type cannot be @code
{
NIL
}
.
Directories may be included by specifying a directory pathname
or namestring in an @code
{
:include
}
directive, e.g.::
(:include "/foo/bar/")
...
...
@@ -2020,6 +2026,12 @@ This allows for packaging software that has file granularity
(
e.g. Debian's @command
{
dpkg
}
or some future version of @command
{
clbuild
}
)
to easily include configuration information about software being distributed.
The convention is that, for sorting purposes,
the names of files in such a directory begin with two digits
that determine the order in which these entries will be read.
Also, the type of these files is conventionally @code
{
"conf"
}
and as a limitation of some implementations, the type cannot be @code
{
NIL
}
.
Directories may be included by specifying a directory pathname
or namestring in an @code
{
:include
}
directive, e.g.:
@verbatim
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment