php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #43814 [GCOV] Compile result links for PECL exts
Submitted: 2008-01-11 08:49 UTC Modified: 2012-06-02 02:08 UTC
From: hannes dot magnusson at gmail dot com Assigned:
Status: Open Package: Website problem
PHP Version: Irrelevant OS: Irrelevant
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
MUST BE VALID
Solve the problem:
18 + 37 = ?
Subscribe to this entry?

 
 [2008-01-11 08:49 UTC] hannes dot magnusson at gmail dot com
Description:
------------
Links to lxr/cvs are pointing to php-src/ext, even for PECL extensions (example: pecl/phar)...


Patches

Add a Patch

Pull Requests

Pull requests:

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2008-01-11 09:12 UTC] bjori@php.net
Errr. I mean on the gcov.php.net site :)
 [2010-05-03 17:38 UTC] philip@php.net
-Status: Assigned +Status: Feedback
 [2010-05-03 17:38 UTC] philip@php.net
I'm unsure if this problem still exists because PECL extensions moved to core are 
[usually] no longer maintained in PECL, and GCOV only tests core. What do you 
think?

In related news, the links are changed from lxr/cvs to og/svn in SVN.
 [2010-05-03 17:56 UTC] hannes dot magnusson at gmail dot com
-Status: Feedback +Status: Open
 [2010-05-03 17:56 UTC] hannes dot magnusson at gmail dot com
Currently it seems to only do core stuff, but at the time of that writing phar 
was in pecl.
I don't see any pecl extensions there now, but the word is pecl/http will be 
enabled soonish - and it will then have the same problem :)
 [2010-05-03 18:29 UTC] philip@php.net
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.
 [2010-05-03 20:31 UTC] nlopess@php.net
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-07 01:50 UTC] philip@php.net
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-08 22:43 UTC] nlopess@php.net
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.
 [2012-06-02 02:08 UTC] nlopess@php.net
-Status: Assigned +Status: Open -Assigned To: nlopess +Assigned To:
 [2019-09-29 09:21 UTC] 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
 
PHP Copyright © 2001-2019 The PHP Group
All rights reserved.
Last updated: Fri Nov 15 12:01:34 2019 UTC