Buildroot软件包管理 [英] Buildroot package management
问题描述
我正在使用buildroot创建在我的ARM平台上运行的rootfs.
I'm using buildroot to create a rootfs running on my ARM platform.
我想在平台上安装一个软件包管理器来轻松安装软件包，例如ubuntu中的apt-get.
I'd like to have a package manager on my platform to easily install packages, like apt-get in ubuntu.
我找到了opkg，可以将其简单地添加到buildroot构建中，但是我找不到有关如何找到存储库的任何信息.
I found opkg, who can be simply added to the buildroot build, but I can't find any information about how to find a repository.
此外，在网络上阅读有关此内容的内容时，我还读到buildroot不包含程序包管理器. opkg不是软件包管理员吗?或者只是某种前端来获取软件包?
Also, reading some stuff on the web about this, I also read that buildroot didn't include a package manager. Isn't opkg a package manager? Or just some kind of frontend to fetch packages?
我不太了解软件包管理器的组成，也没有任何信息.
I don't really understand what a package manager consist of, and I don't find any information about this.
有人可以解释实施这种经理的真正需要是什么，或者在哪里可以找到这种信息?
Could someone explain what is really needed to implement that kind of manager, or where to find such informations?
推荐答案
不是包管理器吗?或者只是某种前端来获取软件包?
Isn't opkg a package manager? Or just some kind of frontend to fetch packages?
opkg 基于
有人可以解释实施这种经理的真正需要什么，或者在哪里可以找到这种信息?
Could someone explain what is really needed to implement that kind of manager, or where to find such information? 包管理器提供许多不同的功能.随着他们的发展，为最终用户增加了不同的舒适度.通常，它们始于Linux 台式机或服务器空间，并已移植用于嵌入式系统. Package managers provide many different features. As they have evolved, different layers of ease for the end user has been added. Generally, they started in the Linux desktop or server space and have been ported for use in embedded systems. 有些差异； 嵌入式系统通常是单任务.软件包管理系统允许用户选择并选择已安装的内容.通常，嵌入式系统可能不想允许用户选择并选择软件包.当然，这取决于应用程序. Some differences; an embedded system is usually single tasked. A package management system allows the user to pick and choose what is installed. Often, an embedded system might not want to allow a user to pick and choose packages. Of course, it depends on the applications. 某些软件包管理功能， RPM ， dpkg ， ipkg 通常仅满足1-4项. Buildroot 甚至不执行此操作，只有第一个项目才是真正相关的.原因是 Buildroot 旨在为永不更新的固定系统构建软件.具有网络更新和程序包迁移的文件系统没有任何意义，因为设备中没有网络连接或外部存储.另外， Buildroot 会尽量减少，并且这些额外的功能会产生一定的成本. Rpm, dpkg, ipkg are typically only fulfilling items 1-4. Buildroot doesn't even do this, only item one is really relevant. The reason is that Buildroot is intended to build software for a fixed system that will never be updated. It doesn't make sense to have a file system with network update and package migration, it there is not network connection or external storage in the device. Also, Buildroot tries to be minimal and these extra features have a cost. LTIB 提供了一个系统来创建项目1-3，但不能创建网络下载.另外，开箱即用的 RPM 大小效率很低.第4项导致典型的开发和部署软件包.为了构建库，您需要头文件来编译依赖的程序包.典型的 LTIB rpm 包含所有头文件.制作排除这些 headers 和 man 页面等的子包是一件容易的事. LTIB provide a system to create items 1-3, but not the network download. Also, out of the box, it is rather in-efficient in RPM size. Item 4, leads to typical devel and deploy packages. In order to build a library, you need header files to compile dependent packages. A typical LTIB rpm includes all the header files. It is an easy task to make sub-packages that exclude these headers and man pages, etc. OpenWrt 非常适合路由器，但是如果您需要图形，声音和其他功能，则软件包可能会不可用.有各种各样的文件系统构建器，但是由于变化的数量，每个都有成本和收益.就像有许多Linux 桌面和服务器发行版一样，有许多具有不同程序包管理选项的 root文件系统构建器.您必须评估您的应用程序和系统的优势. OpenWrt works well for routers, but if you need graphics, sound and other features the packages may not be available. There are various file system builders, but due to the amount of variations, each has costs and benefits. Just as there are many Linux desktop and server distributions, there are many root filesystem builder with different package management options. You have to evaluate the strengths for you application and system. 这篇关于Buildroot软件包管理的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
