https://bugzilla.redhat.com/show_bug.cgi?id=1878468
Petr Pisar <ppisar(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
CC| |ppisar(a)redhat.com
Resolution|--- |NOTABUG
Last Closed| |2020-11-06 12:12:35
--- Comment #4 from Petr Pisar <ppisar(a)redhat.com> ---
(In reply to Dick Franks from comment #3)
Fedora/RHEL end users only install the RPM and are never exposed to
the
tests.
Yes.
Installation of perl-Net-DNS-SEC MUST be a deliberate action by the
end user
who must bear the legal consequences of so doing.
And it so. Installing perl-Net-DNS does not trigger installing
perl-Net-DNS-SEC:
# rpm -q perl-Net-DNS-SEC
package perl-Net-DNS-SEC is not installed
# dnf install perl-Net-DNS
Last metadata expiration check: 0:37:19 ago on Fri 06 Nov 2020 12:24:29 PM CET.
Dependencies resolved.
===========================================================================================================================================
Package Architecture Version
Repository Size
===========================================================================================================================================
Installing:
perl-Net-DNS noarch 1.27-1.fc34
rawhide 368 k
Transaction Summary
===========================================================================================================================================
Install 1 Package
There is no reason for the RPM Perl dependencies not to be in sync
with the
CPAN metadata. From the end-user pov, loading the RPM should be more or less
equivalent to installing from CPAN.
You conflate build-time and run-time dependencies.
The RPM package is built in Fedora infrastructure were BuildRequires are
applied. An owner of the infrastructure takes the legal aspects of the
build-time dependencies seriously <
https://fedoraproject.org/wiki/Licensing>.
The built RPM package is installed on the end user system where BuildRequires
do not apply. And as I showed above it does not trigger installing
perl-Net-DNS-SEC.
The only RPM packages which trigger installing perl-Net-DNS-SEC are
dnssec-tools and dnssec-tools-perlmods.
--
You are receiving this mail because:
You are on the CC list for the bug.