| Message ID | 20210212131733.9926-2-henning.schild@siemens.com |
|---|---|
| State | Superseded, archived |
| Headers | show |
| Series | [1/2] meta-isar: add example recipe for deploying prebuilt debs | expand |
On 12.02.21 14:17, Henning Schild wrote: > From: Henning Schild <henning.schild@siemens.com> > > Signed-off-by: Henning Schild <henning.schild@siemens.com> > --- > doc/user_manual.md | 11 +++++++++++ > 1 file changed, 11 insertions(+) > > diff --git a/doc/user_manual.md b/doc/user_manual.md > index a4f3d1de9d..86bfa99bca 100644 > --- a/doc/user_manual.md > +++ b/doc/user_manual.md > @@ -691,6 +691,17 @@ For the variables please have a look at the previous example, the following new > Have a look at the `example-raw` recipe to get an idea how the `dpkg-raw` class can be used to customize your image. > Note that the package will be build using the whole debian package workflow, so your package will be checked by many debhelper scripts. If those helpers point out quality issues it might be a good idea to fix them. But `example-raw` also shows how rules can still be violated. > > +### Prebuilt .deb packages from somewhere > + > +In some cases you might find yourself having a `.deb` that someone did build, but not a proper debian repository to add to `DISTRO_APT_SOURCES` to get it from. > + > +Such single debs can be included if need be. It is always a better idea to have > +a proper debian repository. > + > +Where you write a recipe that just fetches those debs to its `WORKDIR` and deploys them. They can then be installed via `IMAGE_INSTALL`. > + > +Have a look at `example-prebuilt`. > + > ## Isar Cross-compilation > > ### Motivation > Uups, completely missed that - and did my own quick hack. Let me check the differences... Jan
diff --git a/doc/user_manual.md b/doc/user_manual.md index a4f3d1de9d..86bfa99bca 100644 --- a/doc/user_manual.md +++ b/doc/user_manual.md @@ -691,6 +691,17 @@ For the variables please have a look at the previous example, the following new Have a look at the `example-raw` recipe to get an idea how the `dpkg-raw` class can be used to customize your image. Note that the package will be build using the whole debian package workflow, so your package will be checked by many debhelper scripts. If those helpers point out quality issues it might be a good idea to fix them. But `example-raw` also shows how rules can still be violated. +### Prebuilt .deb packages from somewhere + +In some cases you might find yourself having a `.deb` that someone did build, but not a proper debian repository to add to `DISTRO_APT_SOURCES` to get it from. + +Such single debs can be included if need be. It is always a better idea to have +a proper debian repository. + +Where you write a recipe that just fetches those debs to its `WORKDIR` and deploys them. They can then be installed via `IMAGE_INSTALL`. + +Have a look at `example-prebuilt`. + ## Isar Cross-compilation ### Motivation