By the way I have tested on KDE LiveCD and just by adding cinnamon
repo and running "zypper install cinnamon" everything works out of the
box. I assume some users have a problem with their systems. Everything
is working as intended.
NM
2012/3/17 Nelson Marques
Ralf,
This discussion is off-topic... There is no issue at all with the Build Requirements neither with the Requires. The package has exactly the Requires that it needs to work on GNOME system. The internal RPM dependency generator made a good job and the extra Requires (ex: python-gconf) are present.
The main issue with Cinnamon is that it require the whole GNOME infra-structure present (gnome-session, gsettings, etc) which is installed by GNOME. On KDE users some of those deps aren't pulled/installed properly, furthermore, Cinnamon is built against the GNOME version present in the Distro, so people running other repo's might get issues (which is their own problem, not mine).
The only thing I see to ensure that Cinnamon gets properly deployed on non GNOME installs is to have Requires for all the packages that are part of the GNOME3 pattern... But this is bloating software.... And even if I have a pattern (which exists since day zero), I don't feel it's right to bloat it, neither it solves this issue because if you install the package from http://software.opensuse.org it will still install the package and not the pattern.
This discussion has gone way off-topic, this is a deployment issue under certain conditions and not a build/dependency generator issue.
NM
2012/3/17 Ralf Lang
: 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
-- Nelson Marques // I've stopped trying to understand sandwiches with a third piece of bread in the middle...
-- Nelson Marques // I've stopped trying to understand sandwiches with a third piece of bread in the middle... -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org