Re: new perl release
| From: | Dmitry Stogov | Date: | Mon, 29 Aug 2011 06:13:50 +0000 |
| Subject: | Re: new perl release | ||
| References: | 1 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-8491@lists.php.net to get a copy of this message | ||
Hi Ferenc,
Sorry, I don't have time to maintain this project.
I know that the released version is outdated, and even can't be compiled with recent PHP. I fixed several compatibility issues in trunk, but didn't try to release a new version.
I would appreciate, if you can prepare a new release from the trunk.
Thanks. Dmitry.
On 08/27/2011 11:06 PM, Ferenc Kovacs wrote:
Hi Dmitry, I was browsing through the pecl bugtracker, when I found this: http://pecl.php.net/bugs/bug.php?id=16807 I checked out, and this 1.0.0 release seems completely bogus. I don't know how it was originally released, but there were missing files which made the release uninstallable: /var/lib/peclweb/rest/r/perl/1.0.0.xml /var/lib/peclweb/rest/r/perl/package.1.0.0.xml /var/lib/peclweb/rest/r/perl/deps.1.0.0.txt after manually creating those, I noticed, that the original package cannot be validated against the xml schema, as the notes are missing, which means that even if the above mentioned files are fixed, one still cannot install the package using normal means. to fix this, the package.xml should be updated and the package rebuilt, but I also happen to notice, that the tags in the svn repo also bogus: http://svn.php.net/viewvc/pecl/perl/tags/ there are tags which weren't released and the 1_0_0 tag is much older than the release itself, so I'm not sure what version was used for building the 1.0.0 release. I can see 3 ways to fix this issue: - remove the 1.0.0 release, as it is bogus, and in the future there will be a new version. - create a new release using the source of the 1.0.0 release except fixing the empty<notes> - if the trunk is in such a shape, a new release could be tagged from there (I see some fixes which are newer than the 1.0.0 release) I would like to know what solution would you prefer!