Adding Debian packages: Difference between revisions
(Adding packages: make the use of G_USER_PACKAGES more clear) |
No edit summary |
||
| Line 4: | Line 4: | ||
--> {{PageHeader|{{#var:HARDWARE_NAME}} - Adding Debian Packages}} {{DocImage|category1={{#var:HARDWARE_NAME}}|category2=Debian}} __toc__ | --> {{PageHeader|{{#var:HARDWARE_NAME}} - Adding Debian Packages}} {{DocImage|category1={{#var:HARDWARE_NAME}}|category2=Debian}} __toc__ | ||
= General = | = General = | ||
It's not recommended to duplicate SOM's internal storage/clone from one device to another. There are few scripts run for the first time at startup, and configuration files are generated, which are unique to the SOM. A better approach is to add required packages, services, and applications to the Debian rootfs at compile time using the build script. The resulting rootfs, created by the build script, will then be available as | It's not recommended to duplicate SOM's internal storage/clone from one device to another. There are few scripts run for the first time at startup, and configuration files are generated, which are unique to the SOM. A better approach is to add required packages, services, and applications to the Debian rootfs at compile time using the build script. The resulting rootfs, created by the build script, will then be available as an archive, ready to be deployable for other targets. | ||
Please refer to the {{Varlink2|Debian Build Release|{{#var:RELEASE_LINK}}}} guide to learn more about the build process. | |||
== Adding packages to rootfs == | == Adding packages to rootfs == | ||
Revision as of 19:33, 24 April 2023
General
It's not recommended to duplicate SOM's internal storage/clone from one device to another. There are few scripts run for the first time at startup, and configuration files are generated, which are unique to the SOM. A better approach is to add required packages, services, and applications to the Debian rootfs at compile time using the build script. The resulting rootfs, created by the build script, will then be available as an archive, ready to be deployable for other targets.
Please refer to the Debian Build Release guide to learn more about the build process.
Adding packages to rootfs
If you want to add more packages to the Debian rootfs, add your list of packages to the build script variable G_USER_PACKAGES (already present in the build script).
For example, if you want to add the packages git and vim, you can change
#### user rootfs packages #### readonly G_USER_PACKAGES=""
to
#### user rootfs packages #### readonly G_USER_PACKAGES=" \ git \ vim \ "
File: ~/var_mx8mm_dart_debian_buster/var_make_debian.sh
and build the rootfs according to the Debian Build Release guide.
Adding application to rootfs
If you have your application to be installed on your rootfs:
Take https://github.com/varigit/debian-var/blob/debian_buster_var01/variscite/weston_rootfs.sh#L295
lines as an example and install your applications, config files / settings etc.
Don't forget to copy your resources to variscite folder.
Build the rootfs
Please refer to the Debian Build Release guide to learn how to use the Debian build script to create the rootfs.