![]() TLDP has a dated but very thorough guide on building RPMs. Then provide the metadata needed for the RPM package and package it into an RPM file. For that you need to build the package/library from source and install it into a dummy place (a build root). ![]() When there is no RPM available, you can build it yourself. Therefore, if you follow the convention (called FHS) and keep packages/libraries installed from source in /usr/local, then installing the same library through RPM will not conflict with your library (since the packagers of the distro do follow FHS). RPM) should install their content into /usr. Whilst packages packaged by the distro (e.g. according to the GNU coding standards which most packages follow) a configure script should install its produce into /usr/local. On the other hand, you can have different versions of a library on the same system. RPM packages) and that metadata is the one used to determine dependencies. professional golf) or games that are entirely predictable (simple. ![]() When packaging a distro, the packagers insert the metadata in a specific format into the packages (e.g. It is, in my view, a great pity that such definitions are not put to the test against. Yet, there is no clear-cut integration between the metadata from pkg-config and RPM metadata (or DEB metadata, or pacman metadata). Some configure scripts that build a package from source will produce pkg-config, which is metadata about the installed package. The RPM database only knows about the metadata present in the RPM packages, a package installed from source does not contains this metadata. The RPM dependency database cannot tell that you installed a package from source.
0 Comments
Leave a Reply. |