Re: Soliciting Comments for VersionControl_Hg
| From: | till | Date: | Sat, 09 Jul 2011 21:52:19 +0000 |
| Subject: | Re: Soliciting Comments for VersionControl_Hg | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-54375@lists.php.net to get a copy of this message | ||
On Sat, Jul 9, 2011 at 6:04 PM, Daniel O'Connor
<daniel.oconnor@gmail.com> wrote:
> On Sat, Jul 9, 2011 at 3:29 AM, Michael Gatto <mgatto@lisantra.com> wrote:
>
>>
>> Hi PEAR Devs,
>>
>> I advanced VersionControl_Hg to proposal status a couple weeks ago. I've
>> had
>> some feedback privately, but none officially since the status change.
>>
>> I think we're all poised to vote just about!
>
>
>
>> One thing I could use help on is figuring out where to put the Docbook
>> tutorials in the package's directory structure, and exactly what format
>> they
>> should be in (refentry or article, or...?). I use Pandoc, and am able to
>> convert markdown tutorials to Docbook and then hand-finesse them into
>> usable
>> Docbook files.
>>
> http://pear.php.net/manual/en/developers.documentation.php may
> be of some
> help; as well as browsing
> http://svn.php.net/viewvc/pear/peardoc/trunk/
>
>
>> Also, Changelogs: do these only go into the package.xml file or does PEAR
>> support Unix-style CHANGELOG files in the root?
>>
>> We tend to push it into the package.xml primarily - but there's noting to
> stop you from also including a CHANGELOG file in the package. As far as I
> know no PEAR tools will pick up the content of it though.
Pyrus does something like that.
You could use pyrus to manage your package. You can also create a
PEAR1-compatible package.xml with it. I can help you with it if you
want.
Maybe you want to move to pear2 anyway?
Till