Hi, thanks again however I've experienced a problem while trying to install PhD:
$ pear install package.xml package_generic.xml Cannot install, php_dir for channel "doc.php.net" is not writeable by the current user $ Are all the permissions fine? Thanks, Michal 2013/2/18 Michal Novotny <[email protected]> > Hi, > you're right about CCing the list however I'm using my Gmail over > web-interface so it's easier to forget about it as it's not Thunderbird :-) > Sorry about that. Also, thanks for the links.I really appreciate the links > and I'll read all the guides ASAP. > > Thanks a lot, > Michal > > > 2013/2/18 Ferenc Kovacs <[email protected]> > >> >> >> >> On Mon, Feb 18, 2013 at 10:18 AM, Michal Novotny <[email protected]>wrote: >> >>> Hi, >>> thanks for the account activation and approval. I've already pushed the >>> repository to git.php.net however I would like to make a new release >>> and provide the download. Are there any guidelines how to do it? I can see >>> the "New Release" form at [1] however it requires some package.xml file in >>> the tarball or something. Not really clean what archives are supported, >>> unfortunately I don't see any link to guidelines how to upload/git-generate >>> a new release. >>> >>> Any help would be highly appreciated! >>> >>> Thanks, >>> Michal >>> >>> [1] http://pecl.php.net/release-upload.php >>> >>> >> hi, >> >> please don't top post and don't forget cc'ing the list as you can happen >> to get help from some other subscriber or your question and the answer can >> be useful for somebody else later on. >> to answer your question: the package.xml is a standard pear configuration >> file which used for the packaging a pear/pecl package and by the pear >> server and installer. >> you can read more about the (2nd version) package.xml in the pear >> documentation: >> http://pear.php.net/manual/en/guide.developers.package2.php >> there are only a handful of differences for pecl packages compared to the >> pear packages. >> for creating your package.xml there are a couple of way: >> you can create manually either from scratch or copying from another >> package >> there are also a couple of ways which can help you generate/maintain the >> package.xml (http://pear.php.net/manual/en/pyrus.commands.make.php >> http://pear.php.net/manual/en/pyrus.commands.pickle.php >> http://pear.php.net/manual/en/guide.users.dependencytracking.generatingpackagexml.php) >> when you are done with the package.xml, you should tag your release via >> 'pecl svntag', then 'pecl package' the release and upload it the release on >> pecl.php.net >> I will put together a wiki for this process soon, because it seems to be >> lacking. >> >> ps: watch out to have a recent Archive_Tar package installed, because >> there was a bug (http://pear.php.net/bugs/bug.php?id=19289) fixed in >> version 1.3.9, using previous versions can create corruct releases- >> >> >> -- >> Ferenc Kovács >> @Tyr43l - http://tyrael.hu >> > >
