Re: re-formatting CREDITS file
| From: | Greg Beaver | Date: | Sun, 07 Jun 2009 22:22:06 +0000 |
| Subject: | Re: re-formatting CREDITS file | ||
| References: | 1 2 3 4 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-6462@lists.php.net to get a copy of this message | ||
Lukas Kahwe Smith wrote:
>
> On 08.06.2009, at 00:15, Greg Beaver wrote:
>
>> Pierre Joye wrote:
>>>> The pickle command relies upon a few files to do its magic, such as
>>>>
>>>> README
>>>> CREDITS
>>>> RELEASE-X.Y.Z
>>>>
>>>
>>> Does it support text formatting like markdown or rest? that would
>>> even better.
>>>
>> No, the text is copied verbatim into <summary> <description> and <notes>
>> fields of package.xml (with appropriate encoding and escaping of <
>> and friends).
>>
>> Of course, this is just how I wrote the code, and the best part (I
>> think) about Pyrus is there is a distinct separation of the developer
>> tools from the core installer, thus it will be easy and economical to
>> bloat^H^H^H^Hadd as many features as people need into the developer
>> tools. Personally, I would tend to wonder if the README/CREDITS files
>> are the best place for complex formatting? However, one can easily do a
>> format like wiki markup which is still human-readable, and it solves
>> your problem and mine without any need to change the code.
>
>
> The reST format tries to bridge the need for a non parsed view as well.
> This is what I have started (though never really finished) fo the
> README's in php-src [1]. The README's listed there are simply read
> from CVS and parsed to HTML.
Hi,
I'm all for this, however, if you want ReST validation of these files in
PEAR2_Pyrus_Developer, I will gently ask for an outside contributor to
provide this code (svn access will be readily granted)
:)
Greg