Adding Debian packages: Difference between revisions
(General: some more informations) |
(General: add Debian Build Release link) |
||
| 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. | 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 tarball at {{#var:BUILD_FOLDER}}/output/rootfs.tar.gz, ready to be deployable for other targets. | ||
Please refer to the {{varlink|Debian_Build_Release|{{#var:RELEASE_PARAM}}|Debian Build Release guide}} to learn how to use the build script to create a rootfs. | |||
== Adding Packages to rootfs == | == Adding Packages to rootfs == | ||
Revision as of 02:00, 7 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 tarball at ~/var_mx8mm_dart_debian_buster/output/rootfs.tar.gz, ready to be deployable for other targets.
Please refer to the Debian Build Release guide to learn how to use the build script to create a rootfs.
Adding Packages to rootfs
If you have packages, add your list of packages to build script, while building roofs.
For example, below git and vim
install git, and vim set the line to
readonly G_USER_PACKAGES="git vim"
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
Follow :