|
|
| (36 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| == Caveat ==
| | This is now covered in the [https://docs.yoctoproject.org/dev-manual/common-tasks.html#using-runtime-package-management documentation]. |
| This article is based on work done a few years ago with fido (1.8) and only covers using smart with rpm. Needs some testing and extended to cover using dnf. | |
| | |
| == Complete Build Configuration ==
| |
| Make sure you have done at least one successful build of your target image.
| |
| | |
| == Know Your Package Format ==
| |
| package format is set via variable PACKAGE_CLASSES, typically in local.conf. Look for line like
| |
| PACKAGE_CLASSES ?= "package_rpm"
| |
| This means you're using rpm.
| |
| | |
| == Know Your Package Architectures ==
| |
| Your OS image will be comprised of a number of different package architectures. The package feed needs to know what they are so look in tmp/deploy/rpm
| |
| $ ls tmp/deploy/rpm/
| |
| all core2_32 edison x86_64_nativesdk
| |
| You can exclude anything starting with x86_64. This means you architectures are: <tt>all core2_32 edison</tt>
| |
| | |
| == Select Your Package Feed URL ==
| |
| Is this example we'll use <tt>http://my-server.com/repo</tt>
| |
| | |
| == Configure Package Feed in Build ==
| |
| Now you have the information to create a package feed, ideally you add details in your distro conf file. If you are not using your own distro, you can set the following in local.conf
| |
| PACKAGE_FEED_URIS = "http://my-server.com/repo"
| |
| PACKAGE_FEED_BASE_PATHS = "rpm"
| |
| PACKAGE_FEED_ARCHS = "all edison core2_32"
| |
| | |
| | |
| * select package format
| |
| * PACKAGE_FEED_URIS
| |
| * httpd
| |
| * feed-stability
| |
