Buildroot里面包同治 [英] Buildroot package managment

问题描述

我使用的buildroot创建一个根文件系统在我的ARM平台上运行。

我想有我的平台上的软件包管理器方便的安装包，在Ubuntu apt-get一样。

我发现opkg，谁可以简单地添加到buildroot的身材，但我无法找到有关如何找到一个库中的任何信息。

此外，读一些东西，这个在网络上，我也读到的buildroot不包括的软件包管理器。是不是opkg的软件包管理器？或者只是某种前端去取包？

我真的不明白的软件包管理器组成的，我不觉得这个的任何信息。

有人能解释一下什么是真正需要实现的那种经理，或在哪里可以找到这样的信息？

感谢

解决方案

  

是不是opkg的软件包管理器？或者只是某种前端去取包？

opkg 基于的 的ipkg 。它看起来像它试图提供的所有功能 apt-get的。

  

有人能解释一下什么是真正需要实现的那种经理，或在哪里可以找到这些信息呢？

包管理器提供了许多不同的特点。因为它们已经进化，易于对最终用户的不同层已被添加。一般来说，他们在Linux的启动桌面或服务器的空间，并已经移植用于的嵌入式的系统。

有些差异;一个的嵌入式的系统通常的单任务的。包管理系统允许用户的挑选的安装的是什么。通常，一个的嵌入式的系统可能不希望允许用户的挑选的包。当然，这取决于应用程序。

一些包管理功能，

1. 建筑和修补。


2. 软件包关联，因此包数据库。


3. 包迁移。


4. 包装专业化。


5. 自动下载


6. 尽量减少下载时间/带宽。

用rpm 的dpkg 的ipkg 通常只履行项目1-4。 Buildroot里面甚至没有做到这一点，唯一的项目一个是真正相关。其原因是， Buildroot里面旨在为一个的固定的系统，该系统将永远不会被更新，构建软件。这是没有意义的有网络更新的文件系统和包迁移的，它有没有在网络设备的连接或外部存储。此外， Buildroot里面试图很小而这些额外的功能有代价的。

LTIB 提供一种系统来创建项目1-3，但不是网络下载。此外，开箱即用，这是相当的效率在 RPM 的大小。第4项，导致典型的 DEVEL 和部署包。为了建立一个库，您需要头文件编译依赖的软件包。一个典型的 LTIB转包括所有的头文件。这是一个容易的任务，使的子包的是排除这些的标题的和的人的网页等。

的OpenWrt 非常适用的路由器的，但如果你需要的图形的声音的和其他功能的软件包可能无法使用。有各种文件系统的助洗剂，但由于变化的量，每个具有成本和效益。正如有许多Linux的桌面和服务器发行版的，有很多的根文件系统的建设者用不同的包管理选项。你必须评估你的应用程序和系统的优势。

I'm using buildroot to create a rootfs running on my ARM platform.

I'd like to have a package manager on my platform to easily install packages, like apt-get in ubuntu.

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.

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?

Thanks

解决方案

Isn't opkg a package manager? Or just some kind of frontend to fetch packages?

opkg is based on ipkg. It looks like it tries to provide all the features of apt-get.

Could someone explain what is really needed to implement that kind of manager, or where to find such information?

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.

Some package management features,

1. Building and patching.
2. Package dependency and hence package database.
3. Package migration.
4. Package specialization.
5. Automated download
6. Minimize download time/bandwidth.

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 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 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屋！