Re: [PHP-DEV] module versioning
On Sun, 24 Jun 2001, Andi Gutmans wrote:
> It is not huge amount of work but we should agree on php-dev first about
> what the version number will look like both number wise and format wise,
> i.e. string vs. integer, 1.0.3 vs. 2001008. Probably the latter date is
> more useful in this context.
stig posted a set of really useful ones here:
http://marc.theaimsgroup.com/?l=php-dev&m=98918784106598&w=2
personally, i would like to see something like:
$return = get_ext_version("xml");
where return contains:
$return["number"]["major"] = 4;
$return["number"]["minor"] = 0;
$return["number"]["patch"] = 6;
and
$return["date"][""] = 2001;
$return["date"]["MM"] = 06;
$return["date"]["DD"] = 23;
or similar. what do you think?
dates are ok, but sometimes you have to rush a version out the door twice
on the same day. therefore, i think its probably a good idea to have a MMP
number as well as the date.
- avi
--
PHP Development Mailing List
Re: [PHP-DEV] module versioning
At 06:26 AM 6/24/2001 +0200, Jani Taskinen wrote:
>On Sun, 24 Jun 2001, Andi Gutmans wrote:
>
> >I think we should also consider saving the version in the extension
> >structure and having generic function such as extension_version("xml").
> >This would save us from having to bloat PHP by adding a foo_version()
> >function to all extensions.
>
>Just add one more entry into the module_entry struct?
Yep.
Andi
--
PHP Development Mailing List
Re: [PHP-DEV] module versioning
On Sun, 24 Jun 2001, Andi Gutmans wrote:
>I think we should also consider saving the version in the extension
>structure and having generic function such as extension_version("xml").
>This would save us from having to bloat PHP by adding a foo_version()
>function to all extensions.
Just add one more entry into the module_entry struct?
--Jani
>Andi
>
>At 11:46 AM 6/24/2001 +1000, [EMAIL PROTECTED] wrote:
>
>>this probably should have gone to -dev rather than -cvs.
>>excuse the dual posting.
>>
>>--
>>
>>hello everyone,
>>
>>i am hoping to get the module versioning issue resolved for 4.0.7.
>>
>>1. do any of the core team see it being a problem?
>>2. is someone of suitable knowledge willing to take this one on?
>>
>>http://marc.theaimsgroup.com/?l=php-dev&m=98911444001749&w=2
>>
>>for more information.
>>
>>- avi
>>
>>
>>
>>--
>>PHP Development Mailing List
Re: [PHP-DEV] module versioning
At 02:38 PM 6/24/2001 +1000, [EMAIL PROTECTED] wrote:
>On Sun, 24 Jun 2001, Andi Gutmans wrote:
>
> > I think we should also consider saving the version in the extension
> > structure and having generic function such as extension_version("xml").
> > This would save us from having to bloat PHP by adding a foo_version()
> > function to all extensions.
>
>andi,
>
>thanks for your quick response! i totally agree with your suggestion..
>i think Anil recommended the same thing in the original thread.
>
>will this be much work to implement for 4.0.7?
It is not huge amount of work but we should agree on php-dev first about
what the version number will look like both number wise and format wise,
i.e. string vs. integer, 1.0.3 vs. 2001008. Probably the latter date is
more useful in this context.
>i feel that it would make things a lot cleaner, and will definitely be
>needed if PEAR (the C version) is to have a chance at success.
Andi
--
PHP Development Mailing List
Re: [PHP-DEV] module versioning
On Sun, 24 Jun 2001, Andi Gutmans wrote:
> I think we should also consider saving the version in the extension
> structure and having generic function such as extension_version("xml").
> This would save us from having to bloat PHP by adding a foo_version()
> function to all extensions.
andi,
thanks for your quick response! i totally agree with your suggestion..
i think Anil recommended the same thing in the original thread.
will this be much work to implement for 4.0.7?
i feel that it would make things a lot cleaner, and will definitely be
needed if PEAR (the C version) is to have a chance at success.
- avi
--
PHP Development Mailing List
Re: [PHP-DEV] module versioning
I think we should also consider saving the version in the extension
structure and having generic function such as extension_version("xml").
This would save us from having to bloat PHP by adding a foo_version()
function to all extensions.
Andi
At 11:46 AM 6/24/2001 +1000, [EMAIL PROTECTED] wrote:
>this probably should have gone to -dev rather than -cvs.
>excuse the dual posting.
>
>--
>
>hello everyone,
>
>i am hoping to get the module versioning issue resolved for 4.0.7.
>
>1. do any of the core team see it being a problem?
>2. is someone of suitable knowledge willing to take this one on?
>
>http://marc.theaimsgroup.com/?l=php-dev&m=98911444001749&w=2
>
>for more information.
>
>- avi
>
>
>
>--
>PHP Development Mailing List
