In my opinion, EVERY Build-Require line should get a companion comment about why it's needed. E.g: #Require: package-y not enough, hidden need for path/file from package-z
This way there could be a cronjob on obs that does a "grep -B1 Build-Require *.spec" to find out these sources of Build-Require.
Best would be a automated mail to the maintainers of the not well declared packages that cause the need for Build-Require later.
Yes, there are exemptions, where Build-Require are the best solution, but these are not the cause for most of the trouble missing Require lines in still successful building packages cause.
Cinnamon is just one of the packages where this case hits.
If there would have been a pattern "Cinnamon" from the start, the missing Requires could have been totally overlooked, because the needed packages would have been pulled in by the pattern already.
That said, how should a user react to such a case of missing Require lines, and, could we get a item in the FAQ / Wiki elaborating this, for future reference?
Thanks, - Yamaban.
The packages needed for building (gettext builder for example) and the packages needed for running (web server, database, plugin libraries) can be completely unrelated. While I like comments on requires and BuildRequires (I'm currently building an autogenerator which should mind "manual" entries) I see no relation between Requires and BuildRequires. Moreover, beautifying existing working specs is not a popular task and nagging packagers with reminders for technically irrelevant comments would not make everybody happy. Usually for building you need a lot of -devel stuff which should not be installed just to run a product. -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org