However, present versions of rpmbuild only add deps on library SONAMES, not the library’s full version. Modern package management tools are capable of resolving such dependencies to determine the required packages in many cases. We generally rely on rpmbuild to automatically add dependencies on library SONAMEs. Packages must not contain unnecessary explicit Requires on libraries. Security Updates To Resolve Known CVE IssuesĮxplicit Requires are Requires added manually by the packager in the spec file.Replacing a symlink to a directory or a directory to any type file.
All patches should have an upstream bug link or comment.The package you depend on to provide a directory may choose to own a different directory in a later version and your package will run unmodified with that later version.The directory is owned by a package which is not required for your package to function.The directory is also owned by a package implementing required functionality of your package.The directory is wholly contained in your package, or involves core functionality of your package.Build packages with separate user accounts.Scriplets are only allowed to write in certain directories.Why the %makeinstall macro should not be used.Using % vs $RPM_BUILD_ROOT and $RPM_OPT_FLAGS.Avoid bundling of fonts in other packages.
0 kommentar(er)
