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
Hugo Ishimaru
asdf
Commits
99b16871
Commit
99b16871
authored
14 years ago
by
Francois-Rene Rideau
Browse files
Options
Downloads
Plain Diff
Merge branch 'release' of
ssh://common-lisp.net/project/asdf/public_html/asdf
parents
d4553276
db35f115
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
doc/asdf.texinfo
+18
-2
18 additions, 2 deletions
doc/asdf.texinfo
with
18 additions
and
2 deletions
doc/asdf.texinfo
+
18
−
2
View file @
99b16871
...
@@ -534,7 +534,7 @@ other ASDF add-ons offered the same functionality,
...
@@ -534,7 +534,7 @@ other ASDF add-ons offered the same functionality,
each in subtly different and incompatible ways:
each in subtly different and incompatible ways:
ASDF-Binary-Locations, cl-launch, common-lisp-controller.
ASDF-Binary-Locations, cl-launch, common-lisp-controller.
ASDF-Binary-Locations is now not needed anymore and should not be used.
ASDF-Binary-Locations is now not needed anymore and should not be used.
cl-launch
2.9
00 and common-lisp-controller 7.
1
have been updated
cl-launch
3.0
00 and common-lisp-controller 7.
2
have been updated
to just delegate this functionality to ASDF.
to just delegate this functionality to ASDF.
@node Using ASDF, Defining systems with defsystem, Configuring ASDF, Top
@node Using ASDF, Defining systems with defsystem, Configuring ASDF, Top
...
@@ -2104,7 +2104,7 @@ for configuration by the end-user
...
@@ -2104,7 +2104,7 @@ for configuration by the end-user
in an easy way with configuration files.
in an easy way with configuration files.
Recent versions of same packages use
Recent versions of same packages use
the new @code
{
asdf
-
output
-
translations
}
API as defined below:
the new @code
{
asdf
-
output
-
translations
}
API as defined below:
@code
{
common
-
lisp
-
controller
}
(
7
.
1
)
and @code
{
cl
-
launch
}
(
3
.
00
)
;
@code
{
common
-
lisp
-
controller
}
(
7
.
2
)
and @code
{
cl
-
launch
}
(
3
.
00
0
)
.
@code
{
ASDF
-
Binary
-
Locations
}
is fully superseded and not to be used anymore.
@code
{
ASDF
-
Binary
-
Locations
}
is fully superseded and not to be used anymore.
This incompatibility shouldn't inconvenience many people.
This incompatibility shouldn't inconvenience many people.
...
@@ -2580,6 +2580,12 @@ Naming files within a system definition becomes easy and portable again.
...
@@ -2580,6 +2580,12 @@ Naming files within a system definition becomes easy and portable again.
@code
{
asdf
-
utilities:merge
-
pathnames
*
}
,
@code
{
asdf
-
utilities:merge
-
pathnames
*
}
,
@code
{
asdf::merge
-
component
-
name
-
type
}
.
@code
{
asdf::merge
-
component
-
name
-
type
}
.
On the other hand, there are places where systems used to accept namestrings
where you must now use an explicit pathname object:
@code
{
(
defsystem ... :pathname "LOGICAL
-
HOST:PATH;TO;SYSTEM;" ...
)
}
must now be written with the @code
{
#p
}
syntax:
@code
{
(
defsystem ... :pathname #p"LOGICAL
-
HOST:PATH;TO;SYSTEM;" ...
)
}
@xref
{
The defsystem grammar,,Pathname specifiers
}
.
@xref
{
The defsystem grammar,,Pathname specifiers
}
.
...
@@ -2777,6 +2783,16 @@ See @code{asdf:enable-asdf-binary-locations-compatibility} in
...
@@ -2777,6 +2783,16 @@ See @code{asdf:enable-asdf-binary-locations-compatibility} in
@pxref
{
Controlling where ASDF saves compiled files,,Backward Compatibility
}
.
@pxref
{
Controlling where ASDF saves compiled files,,Backward Compatibility
}
.
But thou shall not load ABL on top of ASDF
2
.
But thou shall not load ABL on top of ASDF
2
.
@item
ASDF pathname designators are now specified in places where they were unspecified,
and a few small adjustments have to be made to some non
-
portable defsystems.
Notably, in the @code
{
:pathname
}
argument to a @code
{
defsystem
}
and its components,
a logical pathname
(
or implementation
-
dependent hierarchical pathname
)
must now be specified with @code
{
#p
}
syntax
where the namestring might have previously sufficed;
moreover when evaluation is desired @code
{
#.
}
must be used,
where it wasn't necessary in the toplevel @code
{
:pathname
}
argument.
@end itemize
@end itemize
Other issues include the following:
Other issues include the following:
...
...
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