-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Wed, 2018-02-21 at 10:51 -0500, Stephen John Smoogen wrote: > On 21 February 2018 at 09:53, Reindl Harald <h.rei...@thelounge.net> > wrote: > > > > > > it's pretty easy: > > > > when you don't list your BuildRequires properly you depend on luck > > that they > > are pulled by something else in the buildroot > > > > OK I understand that, but where is the cutoff. Where as a packager > should I stop adding things and expect that libsolv is going to do > its > job? Do I need to put in > > BuildRequires: kernel > BuildRequires: systemd > BuildRequires: bash > BuildRequires: glibc > ... > > I am depending on luck to get all of those in the environment in a > working variant. I can understand where defining all that would be > useful. I just don't want to spend the next year doing this one by > one > like a death by a thousand papercuts. It would also be a better use > of > the time to have a tool which generated all N dozen items.
No, you don't need kernel/systemd/glibc for build. You do need bash, but this is special case without which RPM wouldn't work. So you are not expected to list those in any case. > > on the other hand there is no point to have GCC in the buildroot > > when you as > > exmaple build phpMyAdmin which is just a bunch of textfiles > > I understand that clearly. What I don't understand is if if gcc-c++ > always pulls in gcc-cc.. why do I need to add that to my manifest? > What is the point of having a libsolver if I have to define what > those > things must depend upon to work? Ask yourself following questions: Do I use g++ myself? Do I use gcc myself? If answer is yes and yes, then list both. If your tool uses just g++, but there is something else inside using gcc, you just list gcc-c++. - -- Igor Gnatenko -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAlqOdDQACgkQaVcUvRu8 X0w9/A/+ONHdx5yTYpVC+kgUHwHSaCv1mfDCZXgoCTQ8kHM8EQvUx2zzsfxmernm kp4xsSHomVmDQ+ftWNV3Qm/ULK7ReQRvjf0JMdtnoK0iLGGOSH1fp8tEtUq3Xnn4 HoWT4pPwIQun+fF3fnd2oJoudCOu9Yrb9o9s3TQhHRSdYxOpCn8Wmv70sum8ulon V0y8g+BqTM5izl/bg/a9bSo7hXlJEk6ohYQgag0eKA1vBIqGE8WaqiopDXEJMLBz 0C1wQEjogsnqfbVZVj4+9ZN6x9rvcyz6OMxy5z6oObnLlMvPfmfq3DfA/bu1ABcq O01eMoio5EYKmRKd1XBhbqZ7+43tot32OTOEwTaUcs3a6XR+BUnzaSDN1EnTWTh5 sCgo/men1psu+og0hqaJkf8UqcWyPzvv01f5WMQxAZyzC3yCNfeCm5P0AGaUcMnp qesi8kNUkTWkB3YNtoWNoslDLexAbMO/yEXpq4Co+eVkKECsZRvBd3AHS5QH+Ot/ 4C1jjR8HbFq59Ki8nNTouk17Nup1WwNp7iSrPAjsUxkpXWOLFIlfidnzXByvqq0i tjaBagqrk22bKaxlroZpF2y2fxmPHypXIUeCiyPllkDIWGgpuXK5CYUzJpykRtzK E6DxHV6jYHqeMX7/H6KrvlcC1dwhE6M7r32f20U3HDqs6SPnLuw= =gLQH -----END PGP SIGNATURE----- _______________________________________________ devel mailing list -- email@example.com To unsubscribe send an email to devel-le...@lists.fedoraproject.org