Electronics & Programming

develissimo

Open Source electronics development and programming

  • You are not logged in.
  • Root
  • » PHP
  • » [PECL-DEV] About that PECL versioning thing [RSS Feed]

#1 March 23, 2008 13:01:53

Hannes M.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

[PECL-DEV] About that PECL versioning thing


On Sun, Mar 23, 2008 at 3:51 AM, Steph Fox <> wrote:
> does anyone have any objection to the proposal at
>http://wiki.php.net/rfc/peclversioning?

The first step in fixing the core<->pecl relationship? \o/

Looks good.
But what about extensions that are symlinked to core? Will they need
to update their version info during core release cycles?
It obviously shouldn't have a -dev version when distributed with PHP..
Is it up to the RM to hunt those extensions down and make sure the
version info is accurate?

-Hannes

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:http://www.php.net/unsub.php

Offline

#2 March 23, 2008 13:40:19

Johannes S.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

[PECL-DEV] About that PECL versioning thing


Hi,

On Sun, 2008-03-23 at 13:01 +0100, "Hannes Magnusson" wrote:
> On Sun, Mar 23, 2008 at 3:51 AM, Steph Fox <> wrote:
> > does anyone have any objection to the proposal at
> >http://wiki.php.net/rfc/peclversioning?
>
> The first step in fixing the core<->pecl relationship? \o/
>
> Looks good.
> But what about extensions that are symlinked to core? Will they need
> to update their version info during core release cycles?
> It obviously shouldn't have a -dev version when distributed with PHP..
> Is it up to the RM to hunt those extensions down and make sure the
> version info is accurate?

Just removing the "-dev" in the version number would be wrong (as is
symlinking), a Stable PHP release should include "stable" extensions.
Not dev versions of the extension. So one of the ideas is to fetch the
last stable extension release for a PHP release, but well, then there's
the problem that everybody (people using snaps, people using CVS, ...)
end up with different versions which makes QA hard. (not to mention bug
hunting trouble with people using the latest release but updated a
single extension, ....)

johannes


--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:http://www.php.net/unsub.php

Offline

#3 March 23, 2008 14:34:43

Steph F.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

[PECL-DEV] About that PECL versioning thing


Hi,The first step in fixing the core<->pecl relationship? \o/That's the basic idea, yes.But what about extensions that are symlinked to core? Will they need
to update their version info during core release cycles?
It obviously shouldn't have a -dev version when distributed with PHP..
Is it up to the RM to hunt those extensions down and make sure the
version info is accurate?Just removing the "-dev" in the version number would be wrong (as is
symlinking), a Stable PHP release should include "stable" extensions.
Not dev versions of the extension. So one of the ideas is to fetch the
last stable extension release for a PHP release, but well, then there's
the problem that everybody (people using snaps, people using CVS, ...)
end up with different versions which makes QA hard. (not to mention bug
hunting trouble with people using the latest release but updated a
single extension, ....)But we already have those problems now. Labelling the version just makes itmore obvious that we have those problems :)- Stephjohannes--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:http://www.php.net/unsub.php

Offline

#4 March 23, 2008 15:08:13

Hannes M.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

[PECL-DEV] About that PECL versioning thing


On Sun, Mar 23, 2008 at 2:34 PM, Steph Fox <> wrote:
> Hi,
>
>
> >> The first step in fixing the core<->pecl relationship? \o/
>
> That's the basic idea, yes.
>
>
> >> But what about extensions that are symlinked to core? Will they need
> >> to update their version info during core release cycles?
> >> It obviously shouldn't have a -dev version when distributed with PHP..
> >> Is it up to the RM to hunt those extensions down and make sure the
> >> version info is accurate?
> >
> > Just removing the "-dev" in the version number would be wrong (as is
> > symlinking), a Stable PHP release should include "stable" extensions.
> > Not dev versions of the extension. So one of the ideas is to fetch the
> > last stable extension release for a PHP release, but well, then there's
> > the problem that everybody (people using snaps, people using CVS, ...)
> > end up with different versions which makes QA hard. (not to mention bug
> > hunting trouble with people using the latest release but updated a
> > single extension, ....)
>
> But we already have those problems now. Labelling the version just makes it
> more obvious that we have those problems :)

Exactly. So lets deal with one problem at a time Johannes.
But Steph: Your RFC doesn't mention how to deal with the problem.
During development the extension should be -dev... so who is
responsible to change it back during PHP releases?

-Hannes

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:http://www.php.net/unsub.php

Offline

#5 March 23, 2008 20:48:51

Steph F.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

[PECL-DEV] About that PECL versioning thing


OK..Just removing the "-dev" in the version number would be wrong (as is
symlinking), a Stable PHP release should include "stable" extensions.
Not dev versions of the extension. So one of the ideas is to fetch the
last stable extension release for a PHP release, but well, then there's
the problem that everybody (people using snaps, people using CVS, ...)
end up with different versions which makes QA hard. (not to mention bug
hunting trouble with people using the latest release but updated a
single extension, ....)Temporary halfway-house solution: don't tag the symlinked extensionswith -dev for now, just call them 1.0.0 or whatever. We can move to properversioning for those symlinked ones when we have a way to bring stable PECLpackages into core, but at least there'll be a structure already in placethat makes that easy.- Stephjohannes--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:http://www.php.net/unsub.php

Offline

#6 March 24, 2008 12:27:37

Pierre J.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

[PECL-DEV] About that PECL versioning thing


On Sun, Mar 23, 2008 at 3:51 AM, Steph Fox <> wrote:
> Hi all,
>
> Since I'm still awake at 3am...
>
> Aside from Pierre's arguments in favour of using package.xml to set the
> extension version (which 3 PECL extensions - two of them Pierre's - do at
> present), does anyone have any objection to the proposal at
>http://wiki.php.net/rfc/peclversioning?

I'm not in favour of using package.xml to set the version. I'm in
favour of allowing package.xml usage.

Now, why cross posting, adding a random set of the pecl-dev
discussions as comments in the wiki? And the rules about what means a
version increment is missing.

The wiki is a publication media, the lists are the discussion
media.pecl-dev in this case is the right list.

As far as I remember, php-src did not want to have per extension
versions. However, It is fine to add an information about its version
to help the users to know if the pecl releases is newer than the
bundled version. Can we please keep the discussions in on list? It is
already hard enough to follow everything.

> I discovered tonight that I have full PECL karma, so the secondary question
> is: does anyone have any objection to my making all (or most... I'd leave
> the package.xml ones for now) PECL modules fit this versioning model?

Many extensions use branches, I would go with a patch posted to
pecl-dev and let the respective maintainers apply it to the active
branches. (zip has two branches + php-src).

Cheers,
--
Pierrehttp://blog.thepimp.net|http://www.libgd.org--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:http://www.php.net/unsub.php

Offline

#7 March 25, 2008 10:52:07

Hartmut H.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

[PECL-DEV] About that PECL versioning thing


Steph Fox wrote:I discovered tonight that I have full PECL karma, so the secondaryquestion is: does anyone have any objection to my making all (or most...I'd leave the package.xml ones for now) PECL modules fit this versioningmodel?i'm fine with it, and i already changed pecl-gen / CodeGen_PECL
to create compliant code. I didn't roll a new release yet though
waiting for the final outcome of this ...

--
Hartmut Holzgraefe, Principal Support Engineer
.
Discover new MySQL Monitoring & Advisory features at:http://www.mysql.com/products/enterprise/whats_new.htmlHauptsitz: MySQL GmbH, Dachauer Str.37, 80335 München
Geschäftsführer: Kaj Arnö - HRB München 162140


--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:http://www.php.net/unsub.php

Offline

#8 March 25, 2008 11:08:25

Pierre J.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

[PECL-DEV] About that PECL versioning thing


On Tue, Mar 25, 2008 at 10:44 AM, Hartmut Holzgraefe <> wrote:
> Steph Fox wrote:
>
> > I discovered tonight that I have full PECL karma, so the secondary
> > question is: does anyone have any objection to my making all (or most...
> > I'd leave the package.xml ones for now) PECL modules fit this versioning
> > model?
>
> i'm fine with it, and i already changed pecl-gen / CodeGen_PECL
> to create compliant code. I didn't roll a new release yet though
> waiting for the final outcome of this ...


I think you can go ahead with the #define PHP__VERSION part, we
all agree on that already ( I will update the wiki later today). Not
sure if the rest affects codegen, do you check the version format
itself or do you realy on the pear installer for this task?

Cheers,
--
Pierrehttp://blog.thepimp.net|http://www.libgd.org--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:http://www.php.net/unsub.php

Offline

#9 March 25, 2008 11:13:00

Hartmut H.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

[PECL-DEV] About that PECL versioning thing


Pierre Joye wrote:Not
sure if the rest affects codegen, do you check the version format
itself or do you realy on the pear installer for this task?it is not checked yet, but it is an open TODO item anyway ...

--
Hartmut Holzgraefe, Principal Support Engineer
.
Discover new MySQL Monitoring & Advisory features at:http://www.mysql.com/products/enterprise/whats_new.htmlHauptsitz: MySQL GmbH, Dachauer Str.37, 80335 München
Geschäftsführer: Kaj Arnö - HRB München 162140


--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:http://www.php.net/unsub.php

Offline

#10 March 25, 2008 16:09:57

Steph F.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

[PECL-DEV] About that PECL versioning thing


Hi Hartmut,I discovered tonight that I have full PECL karma, so the secondaryquestion is: does anyone have any objection to my making all (or most...I'd leave the package.xml ones for now) PECL modules fit this versioningmodel?i'm fine with it, and i already changed pecl-gen / CodeGen_PECL
to create compliant code. I didn't roll a new release yet though
waiting for the final outcome of this ...

Cool :) thanks!

- Steph

--
Hartmut Holzgraefe, Principal Support Engineer
.
Discover new MySQL Monitoring & Advisory features at:http://www.mysql.com/products/enterprise/whats_new.htmlHauptsitz: MySQL GmbH, Dachauer Str.37, 80335 München
Geschäftsführer: Kaj Arnö - HRB München 162140


--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:http://www.php.net/unsub.php

Offline

  • Root
  • » PHP
  • » [PECL-DEV] About that PECL versioning thing [RSS Feed]

Board footer

Moderator control

Enjoy the 16th of December
PoweredBy

The Forums are managed by develissimo stuff members, if you find any issues or misplaced content please help us to fix it. Thank you! Tell us via Contact Options
Leave a Message
Welcome to Develissimo Live Support