Changeset ad7f3b7
- Timestamp:
- 03/20/2023 07:27:31 AM (13 months ago)
- Branches:
- 12.0, 12.1, kea, ken/TL2024, ken/tuningfonts, lazarus, lxqt, plabs/newcss, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/llvm18, xry111/xf86-video-removal
- Children:
- 21114f6
- Parents:
- 686afa98
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/important/building-notes.xml
r686afa98 rad7f3b7 456 456 <quote>runtime</quote>, which means the target package can be built but 457 457 cannot function without it.</para> 458 <para> 459 Note that a target package can start to <quote>function</quote> 460 in many subtle ways: an installed configuration file can make the 461 init system, cron daemon, or bus daemon to run a program 462 automatically; another package using the target package as an 463 dependency can run a program from the target package in the 464 building system; and the configuration sections in the BLFS book 465 may also run a program from a just installed package. So if 466 you are installing the target package without a 467 <emphasis>Required (runtime)</emphasis> dependency installed, 468 You should install the dependency as soon as possible after the 469 installation of the target package. 470 </para> 458 471 </listitem> 459 472 <listitem> … … 472 485 <para><emphasis>Optional</emphasis> means that this package might be 473 486 installed for added functionality. Often BLFS will describe the 474 dependency to explain the added functionality that will result.</para> 475 </listitem> 476 <listitem> 477 <para><emphasis>Runtime</emphasis> means this package is not needed 478 to install the target package, but when you run a program from the 479 target package or a program using a library from the target 480 package, it may lack some functionality or even crash immediately. 481 Based on the importance of the lacked functionality, the Runtime 482 dependencies are further labeled as Required, Recommended, or 483 Optional. You can install a Runtime dependency to recover the 484 lacked functionality of the target package, without rebuilding the 485 target package itself.</para> 486 <para> 487 Note that a target package can start to <quote>run</quote> in 488 many subtle ways: an installed configuration file can make the 489 init system, cron daemon, or bus daemon to run a program 490 automatically; another package using the target package as an 491 dependency can run a program from the target package in the 492 building system; and the configuration sections in the BLFS book 493 may also run a program from a just installed package. So if 494 you are installing the target package without a 495 <emphasis>Required (Runtime)</emphasis> dependency installed, 496 You should install the dependency as soon as possible after the 497 installation of the target package. 498 </para> 487 dependency to explain the added functionality that will result. 488 An optional dependency may be automatically pick up by the target 489 package if the dependency is installed, but another some optional 490 dependency may also need additional configuration options to enable 491 them when the target package is built. Such additional options are 492 often documented in the BLFS book. If an optional dependency is 493 said to be <quote>runtime</quote>, it means you may install 494 the dependency after installing the target package to support some 495 optional features of the target package if you need these 496 features.</para> 497 <para>An optional dependency may be out of BLFS. If you need such 498 an <emphasis>external</emphasis> optional dependency for some 499 features you need, read <xref linkend='beyond'/> for the general 500 hint about installing an out-of-BLFS package.</para> 499 501 </listitem> 500 502 </itemizedlist>
Note:
See TracChangeset
for help on using the changeset viewer.