 |
 |
 |
 |
 |
friends fun |
J&P Group > J&P InfoSol > Applications > Package Managers (apt, dpkg, port, rpm, ...)
| Linux Distros | BSD-Based | Mac OS X | |||
|---|---|---|---|---|---|
| Base/Origin | Debian | Slackware | RedHat | BSD | (BSD-core) |
| Derivates / More known distros1 | Knoppix, Ubuntu | Suse | CentOS | FreeBSD, NetBSD, OpenBSD | Mac OS X 10.x |
| Primary Pkg Mgr(s) |
apt, dpkg | pkgtool | rpm | google to learn more | |
| 1Aside base/origin distros. | |||||
(2014 Oct)
Use cases:
| Functionality needs: | How advanced capabilities do we really need? |
| Overhead: | For learning how to actually package files for some more capable package manager system ('PMS') In building and maintaining, cross-compiling, PMS tool(s) for use on embedded systems. |
| Availability: | If PMS even available for cross compilation on your target env? |
| Footprint (size) | How much resources will PMS take up on embedded system? |
Example, specific case Oct 2014
Package Manager Solution |
Runtime Env. | |||
|---|---|---|---|---|
Host* |
Target w/ |
Fetch |
|
|
APT – Advanced Package Tool |
Yes |
No |
Yes |
|
dpkg – for Debian package mgmt. |
Yes |
Yes |
No |
|
RPM Package Manager (RedHat) |
No |
Yes |
No |
|
Legend:
Host – whether package exist in development environment host (*Debian 7.6 in this case), if exist simplifies dev and test of packages, as doesn’t have to get and build package also for this environment.
BusyBox – whether functionality is available in this package, not that we’re currently including among options when building it.
Fetch – whether package include capabilities to also fetch packages from remote destination
