lagertonne/ifupdown-ng
1
0
Fork 0
Code Issues Pull requests Projects Releases 4 Wiki Activity

README: requires keyword is not necessarily required anymore

Browse source
This commit is contained in:
Ariadne Conill 2020-08-18 14:42:30 -06:00
parent b9efc841a3
commit f282704186
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -8,10 +8,10 @@ ifupdown, BusyBox ifupdown and Cumulus Networks' ifupdown2.
![Dependency resolution example](doc/img/dependency-resolution.png) ![Dependency resolution example](doc/img/dependency-resolution.png)
ifupdown-ng uses a dependency resolver to determine interface bring-up order ifupdown-ng uses a dependency resolver to determine interface bring-up order
in a deterministic way. To use this feature, you must declare relationships in a deterministic way.
between interfaces with the `requires` keyword. This keeps the implementation
efficient. For convenience, the `requires` keyword is exported to executors This is accomplished through a combination of manual hinting using the `requires`
as the `IF_REQUIRES` environment variable. keyword and dependency learning using native executors.
For compatibility with some legacy ifupdown executors, we also provide the For compatibility with some legacy ifupdown executors, we also provide the
`requires` keyword under other environment variables in some cases. `requires` keyword under other environment variables in some cases.