FC4 perl module upgrades/cleanups

[Jeff Johnson]

Chris Adams wrote:

>>* %define _use_internal_dependency_generator 0
>>Many of the ancient specs have this.  Might be nice to get rid of it, 
>>but it will require some careful verification comparing the before and 
>>after in order to be sure the rpm-auto-dep isn't demanding bad 
>>dependencies like Win32 crap.  Is this worth doing?  Need your opinions.
>>    
>>
>
>I only use it when I need to strip out a dependency.  When I need it, I
>put the following in my %install:
>
># Strip out some dependencies
>cat > find-requires.sh <<'EOF'
>exec %{__find_requires} "$@" | egrep -v '^perl\((Crypt::IDEA|Term::ReadKey)\)$'
>EOF
>chmod +x find-requires.sh
>%define _use_internal_dependency_generator 0
>%define __find_requires %{_builddir}/%{buildsubdir}/find-requires.sh
>
>I prefer doing it this way instead of with an extra Source*: script;
>this way, the script is generated on the fly (especially useful when
>using the same SRPM on multiple platforms, where find-requires may not
>be in /usr/lib/rpm).  It also makes the stripped out dependencies part
>of the spec file directly.
>  
>

Adding

     %define _use_internal_dependency_generator 0

is very much the wrong thing to do with any package that includes elf32/elf64 modules.

And there is loss of functionality if/when %_use_internal_dependency_generator is used
for any package, as dependencies are not attached to files.

The mechanism was intended to to assist bootstrapping multilib, not for serious packaging usage.

73 de Jeff