Edit report at https://bugs.php.net/bug.php?id=43814&edit=1

 ID:                 43814
 Updated by:         [email protected]
 Reported by:        hannes dot magnusson at gmail dot com
 Summary:            [GCOV] Compile result links for PECL exts
 Status:             Open
 Type:               Bug
 Package:            Website problem
 Operating System:   Irrelevant
 PHP Version:        Irrelevant
 Block user comment: N
 Private report:     N

 New Comment:

I think we should decomission gcov.php.net, unless somebody is
willing to spend time on making it work with recent PHP version.
The last successful coverage report of PHP 7.4 is from
2019-05-08[1].

[1] <http://gcov.php.net/PHP_7_4/lcov_html/>


Previous Comments:
------------------------------------------------------------------------
[2019-09-29 09:21:36] Vitalii dot havaretskyi at gmail dot com

The following pull request has been associated:

Patch Name:  Replace http:// to https://
On GitHub:  https://github.com/php/web-php/pull/287
Patch:      https://github.com/php/web-php/pull/287.patch

------------------------------------------------------------------------
[2010-05-08 22:43:04] [email protected]

The information is not available to the frontend right now.
A "simple" fix is to do a "svn info" on each extensions' dir and check if the 
url matches pecl or not. Or even have a generic scheme that builds the URL from 
a generic PHP svn path.

------------------------------------------------------------------------
[2010-05-07 01:50:59] [email protected]

Nuno, any suggestions for how to fix this bug? In other words, is the 
information 
(which PECL extensions are enabled) available to site.api.php? Can it be?

------------------------------------------------------------------------
[2010-05-03 20:31:16] [email protected]

I add new extensions on a per-request basis. This problem only shows up if the 
extension only lives in PECL.
pecl/http was disabled since it was breaking the build too often, and the 
authors didn't fix the problem quickly enough. Of course it can be reenabled 
again if the authors promise they will only commit stuff after (at least) 
successful compilation.

------------------------------------------------------------------------
[2010-05-03 18:29:05] [email protected]

So extensions that will/may move to core into the future are added? Okay, that 
makes sense, this shouldn't be too difficult. A fix will likely take place once 
we 
get the official OpenGrok box up and running.

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=43814


--
Edit this bug report at https://bugs.php.net/bug.php?id=43814&edit=1

-- 
PHP Webmaster List Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to