[openFate 305727] rpmbuild build should warn about possibly by mistake %excluded files
Feature added by: Stephan Binner (Beineri) Feature #305727, revision 1, last change by Title: rpmbuild build should warn about possibly by mistake %excluded files openSUSE-11.2: New Priority Requester: Desirable Requested by: Stephan Binner (beineri) Partner organization: openSUSE.org Description: If one works with %exclude macros in %files sections, esp with several sub-packages and wildcards in the %exclude statements, then it can easily happen that files installed to the RPM_BUILD_ROOT do not get packaged into a package at all. This case happens currently completely silent. rpmbuild should warn when an installed file gets only referenced by an %exclude statement but nowhere else. An option might be to make this warning a build error and to have a policy to allow installed files to be excluded from packages by well visible "rm $RPM_BUILD_ROOT/foo" calls within the .spec only. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305727
Feature changed by: Michael Löffler (michl19) Feature #305727, revision 4 Title: rpmbuild build should warn about possibly by mistake %excluded files - openSUSE-11.2: New + openSUSE-11.2: Evaluation Priority Requester: Desirable Requested by: Stephan Binner (beineri) Description: If one works with %exclude macros in %files sections, esp with several sub-packages and wildcards in the %exclude statements, then it can easily happen that files installed to the RPM_BUILD_ROOT do not get packaged into a package at all. This case happens currently completely silent. rpmbuild should warn when an installed file gets only referenced by an % exclude statement but nowhere else. An option might be to make this warning a build error and to have a policy to allow installed files to be excluded from packages by well visible "rm $RPM_BUILD_ROOT/foo" calls within the .spec only. -- openSUSE Feature: https://features.opensuse.org/305727
Feature changed by: Stephan Kulow (coolo) Feature #305727, revision 5 Title: rpmbuild build should warn about possibly by mistake %excluded files - openSUSE-11.2: Evaluation + openSUSE-11.2: Rejected by Stephan Kulow (coolo) + reject date: 2009-06-24 12:02:57 + reject reason: see comment Priority Requester: Desirable Requested by: Stephan Binner (beineri) Description: If one works with %exclude macros in %files sections, esp with several sub-packages and wildcards in the %exclude statements, then it can easily happen that files installed to the RPM_BUILD_ROOT do not get packaged into a package at all. This case happens currently completely silent. rpmbuild should warn when an installed file gets only referenced by an % exclude statement but nowhere else. An option might be to make this warning a build error and to have a policy to allow installed files to be excluded from packages by well visible "rm $RPM_BUILD_ROOT/foo" calls within the .spec only. + Discussion: + #1: Stephan Kulow (coolo) (2009-06-24 12:02:38) + I claim it's the whole purpose of %exclude to be able to ignore + installed files. and so your feature doesn't make sense. -- openSUSE Feature: https://features.opensuse.org/305727
Feature changed by: Pavol Rusnak (prusnak) Feature #305727, revision 6 Title: rpmbuild build should warn about possibly by mistake %excluded files openSUSE-11.2: Rejected by Stephan Kulow (coolo) reject date: 2009-06-24 12:02:57 reject reason: see comment Priority Requester: Desirable Requested by: Stephan Binner (beineri) Description: If one works with %exclude macros in %files sections, esp with several sub-packages and wildcards in the %exclude statements, then it can easily happen that files installed to the RPM_BUILD_ROOT do not get packaged into a package at all. This case happens currently completely silent. rpmbuild should warn when an installed file gets only referenced by an % exclude statement but nowhere else. An option might be to make this warning a build error and to have a policy to allow installed files to be excluded from packages by well visible "rm $RPM_BUILD_ROOT/foo" calls within the .spec only. Discussion: #1: Stephan Kulow (coolo) (2009-06-24 12:02:38) I claim it's the whole purpose of %exclude to be able to ignore installed files. and so your feature doesn't make sense. + #2: Pavol Rusnak (prusnak) (2009-06-30 01:51:37) (reply to #1) + Actually it does. If you don't want to put the file into any of the + subpackages you should remove it in the %install phase or do not + install it at all. The %exclude macro usage is then limited to usecase + when one package contains e.g. %{_bindir}/* in filelist and the other + has %{_bindir}/foo. (In this case the foo should be %excluded in the + first package). -- openSUSE Feature: https://features.opensuse.org/305727
participants (1)
-
fate_noreply＠suse.de