[Bug 831716] Moving legacy code out of perl-JSON-RPC breaks Bugzilla

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=831716

Emmanuel Seyman <emmanuel.seyman at club-internet.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #4 from Emmanuel Seyman <emmanuel.seyman at club-internet.fr> ---
(In reply to comment #0)
>
> So the legacy code is still required by Bugzilla, and checksetup.pl and
> Bugzilla re confused by this package split.

The split is there so that:

a) People can have the legacy code installed without having to install the new
(incompatible) version along with it
b) People can have the new version installed and be sure that the old version
isn't used

Obviously, this is of no use if you need both. And this module is in Fedora for
the sole reason that Bugzilla uses it.

(In reply to comment #2)
> 
> You can check for `perl(JSON::RPC::Legacy::Server::CGI)' RPM Provides or by
> perl code `eval q{use JSON::RPC::Legacy::Server::CGI; 1} or die q{Missing};'

The problem here is that JSON-RPC is an optional feature in Bugzilla. I'm
really not keen on making the package require optional features.

(In reply to comment #3)
> 
> This is exactly what Bugzilla does. It looks for JSON::RPC. This is supposed
> to mean that legacy code is also installed. Bugzilla is not going to check
> each module individually. JSON::RPC is not supposed to be split into several
> pieces, which is specific to Fedora/RHEL.

TBH, all Linux distributions split the core perl distribution in a number of
ways. I'm not sure there's a point to arguing that this can't be done for
non-core modules.

-- 
You are receiving this mail because:
You are on the CC list for the bug.