FAQ
Edit report at http://pear.php.net/bugs/bug.php?id=10949&edit=1

ID: 10949
Updated by: cweiske@php.net
Reported By: daniel dot oconnor at gmail dot com
Summary: Allow preview of .tar.gz files during pepr proposal
process
-Status: Open
+Status: Wont fix
Type: Feature/Change Request
Package: pearweb
Package Version: 1.15.0
PHP Version: 5.2.1
-Roadmap Versions: 1.19.0
+Roadmap Versions:
New Comment:

-Status: Open
+Status: Wont fix
-Roadmap Versions: 1.19.0
+Roadmap Versions:



Previous Comments:
------------------------------------------------------------------------

[2008-02-06 18:31:42] cellog

if I install pecl/phar 2.0.0 on pearweb, we can use it to browse .tgz
files. First it needs to be released.

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

[2007-06-10 20:32:15] dufuz

This sounds like a very useful feature, we'll look into it, hopefully
in time for 1.17

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

[2007-05-06 05:56:35] doconnor

Description:
------------
All too often we see comments like:

Martin Jansen (http://pear.php.net/user/mj) has commented on the
proposal for PHP::PHP_DocBlock.

Comment:
Can you put .phps files online somewhere? This way it is easier to
browse through your source code. Thanks!


This should not be necessary.
The pepr proposal UI indicates that it's fine to upload a .tar.gz; and
pear developers almost never look at them.

Thus:
A quick and easy browser for .tar.gz files as .phps would be very
useful.

Expected sequence of events:
1. Proposal is submitted, and a .tar.gz is attached
2. No .phps exists
3. pearweb extracts the .tar.gz
4. pearweb runs any checks on it (ie, code sniffing via
PHP_CodeSniffer or validating the package.xml)
5. pearweb generates phpdocs and source code as phps files and
provides links
6. Existing pear developers are then much more able to examine
packages.

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

Search Discussions

  • Daniel Oconnor at Aug 24, 2009 at 1:16 am
    Edit report at http://pear.php.net/bugs/bug.php?id=10949&edit=1

    ID: 10949
    Updated by: daniel.oconnor@gmail.com
    Reported By: daniel dot oconnor at gmail dot com
    Summary: Allow preview of .tar.gz files during pepr proposal
    process
    Status: Wont fix
    Type: Feature/Change Request
    Package: pearweb
    Package Version: 1.15.0
    PHP Version: 5.2.1
    Roadmap Versions:
    New Comment:

    If we're gonna wfx it, can we change the pepr UI to point out how
    important it is to provide browseable source as well?


    Previous Comments:
    ------------------------------------------------------------------------

    [2009-08-23 11:34:32] cweiske

    -Status: Open
    +Status: Wont fix
    -Roadmap Versions: 1.19.0
    +Roadmap Versions:


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

    [2008-02-06 18:31:42] cellog

    if I install pecl/phar 2.0.0 on pearweb, we can use it to browse .tgz
    files. First it needs to be released.

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

    [2007-06-10 20:32:15] dufuz

    This sounds like a very useful feature, we'll look into it, hopefully
    in time for 1.17

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

    [2007-05-06 05:56:35] doconnor

    Description:
    ------------
    All too often we see comments like:

    Martin Jansen (http://pear.php.net/user/mj) has commented on the
    proposal for PHP::PHP_DocBlock.

    Comment:
    Can you put .phps files online somewhere? This way it is easier to
    browse through your source code. Thanks!


    This should not be necessary.
    The pepr proposal UI indicates that it's fine to upload a .tar.gz; and
    pear developers almost never look at them.

    Thus:
    A quick and easy browser for .tar.gz files as .phps would be very
    useful.

    Expected sequence of events:
    1. Proposal is submitted, and a .tar.gz is attached
    2. No .phps exists
    3. pearweb extracts the .tar.gz
    4. pearweb runs any checks on it (ie, code sniffing via
    PHP_CodeSniffer or validating the package.xml)
    5. pearweb generates phpdocs and source code as phps files and
    provides links
    6. Existing pear developers are then much more able to examine
    packages.

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

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppear-bugs @
categoriesphp
postedAug 23, '09 at 9:34a
activeAug 24, '09 at 1:16a
posts2
users2
websitepear.php.net

2 users in discussion

Daniel Oconnor: 1 post Cweiske: 1 post

People

Translate

site design / logo © 2022 Grokbase