Everything

php

question on policy of renaming an extension

php.internals

Brad House

22 years ago

The ext/mcve module at some point in time needs to be renamed
ext/monetra to reflect a naming change, and lessen confusion
in the field, as the product is no longer referenced as MCVE.

What is the best way to go about doing this? I did not want to
just go in there and remove ext/mcve and commit the same stuff
to ext/monetra and 'get in trouble'. (Truthfully, I don't know
if I even have the perms to do this).

At this point there are only minimal changes needed to take
advantage of the new naming (primarily the config.m4 and a
couple of small references elsewhere), as the function calls
and variables already reflect the change.

Thanks!

-Brad

Derick Rethans

22 years ago

On Sun, 20 Jun 2004, Brad House wrote:

> The ext/mcve module at some point in time needs to be renamed
> ext/monetra to reflect a naming change, and lessen confusion
> in the field, as the product is no longer referenced as MCVE.
>
> What is the best way to go about doing this? I did not want to
> just go in there and remove ext/mcve and commit the same stuff
> to ext/monetra and 'get in trouble'. (Truthfully, I don't know
> if I even have the perms to do this).

The way to do this is:
(on the cvs server):
cp -r mcve montra

then on the client side with CVS:

cvs delete mcve
cvs commit mcve (or similar)

Derick

Brad House

22 years ago

heh, well, I know I definitely do not have permissions
to do that then :)
Any assistance someone could provide me would be appreciated.
Also, I can go ahead an make a set of patches to finalize
the naming switch for the config.m4/w32 and the remaining
references in the code (and commit prior to renaming the
directory if desired).

Thanks!
-Brad

Derick Rethans wrote:

Derick Rethans

22 years ago

On Sun, 20 Jun 2004, Brad House wrote:

> heh, well, I know I definitely do not have permissions
> to do that then :)
> Any assistance someone could provide me would be appreciated.
> Also, I can go ahead an make a set of patches to finalize
> the naming switch for the config.m4/w32 and the remaining
> references in the code (and commit prior to renaming the
> directory if desired).

I would do that after, so that people can still checkout the old
extension and use it with the old name.

Derick

Jan Lehnardt

22 years ago

Hi,
On 20 Jun 2004, at 17:36, Brad House wrote:

> Any assistance someone could provide me would be appreciated.
> Also, I can go ahead an make a set of patches to finalize
> the naming switch for the config.m4/w32 and the remaining
> references in the code (and commit prior to renaming the
> directory if desired).

Why not take the opportunity and move the extension to PECL?
It sounds like a good candidate.

Jan

--
GPG Key: BB96 56B0
Q: Thank Jan? - A: http://geschenke.an.dasmoped.net/

Brad House

22 years ago

>
> Why not take the opportunity and move the extension to PECL?
> It sounds like a good candidate.

Well, PECL still seems a bit like the redheaded step-child. I cannot
even seem to reference it in the php documentation online (except for
seeing some modules have been moved there).
There are quite a few users that utilize this extension, including
enterprise clients like Thrifty Car Rental, which I'd rather not
inconvenience if possible.
When PECL is better adopted by the community, and PHP provides
documentation on them, I would have no problem moving it there.

Thanks.

--
-----------------------------
Brad House
Sr. Developer
Main Street Softworks, Inc.

brad@mainstreetsoftworks.com
(386) 462-9522 Ext. 112
-----------------------------

Rasmus Lerdorf

22 years ago

On Sun, 20 Jun 2004, Brad House wrote:

> Well, PECL still seems a bit like the redheaded step-child. I cannot
> even seem to reference it in the php documentation online (except for
> seeing some modules have been moved there).
> There are quite a few users that utilize this extension, including
> enterprise clients like Thrifty Car Rental, which I'd rather not
> inconvenience if possible.
> When PECL is better adopted by the community, and PHP provides
> documentation on them, I would have no problem moving it there.

What do you mean provides documentation on them?  PECL extensions are
documented right next to any other extension, providing someone has
written the documentation, of course.  You didn't find special pecl
extension documentation precisely because pecl extensions are perfectly
integrated so the end user has no idea that they are even using one.

Did you know that ext/oci8, ext/tidy, ext/simplexml and ext/sqlite and
ext/bz2 are all actually pecl extensions for example?

And yes, I agree with others that this should go to PECL now.

-Rasmus

Jan Lehnardt

22 years ago

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,
On 20 Jun 2004, at 19:42, Brad House wrote:

> When PECL is better adopted by the community, and PHP provides
> documentation on them, I would have no problem moving it there.

Following Rasmus' mail, moving your extension also increases
the convenience for you the developer and the users.
As a developer you're no longer tied to PHP's release
schedule, but you are free to release a new version whenever
you want. For the users of your extension it means, they can
have an updated version (be it a bug- or security-fix) anytime
you release it and not only when a PHP version comes out.

Installing a PECL based extension is as easy as
$ pear install foobar

See http://pecl.php.net/ for more information.

Jan
- --
GPG Key: BB96 56B0
Q: Thank Jan? - A: http://geschenke.an.dasmoped.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)

iD8DBQFA1dH07KW8t7uWVrARAgl6AKCYOnflBFVhdoBWtLMOryG7KGskAwCfRhK5
xSnFluy8FsfkWMSrgw9jqOw=
=lJp+
-----END PGP SIGNATURE-----

Rasmus Lerdorf

22 years ago

Please don't associate being moved to PECL with whether or not the
extension is distributed as a standard PHP extension in the distribution
tarball or not.  The two have nothing to do with each other.

-Rasmus

On Sun, 20 Jun 2004, Jan Lehnardt wrote:

Brad House

22 years ago

I was under the impression that it was one or the other, not
both.  How do you coordinate the 2?

-Brad

Rasmus Lerdorf wrote:

> Please don't associate being moved to PECL with whether or not the
> extension is distributed as a standard PHP extension in the distribution
> tarball or not.  The two have nothing to do with each other.
>
> -Rasmus
>
> On Sun, 20 Jun 2004, Jan Lehnardt wrote:
>
>
>>--[PinePGP]--------------------------------------------------[begin]--
>>Hi,
>>On 20 Jun 2004, at 19:42, Brad House wrote:
>>
>>>When PECL is better adopted by the community, and PHP provides
>>>documentation on them, I would have no problem moving it there.
>>
>>Following Rasmus' mail, moving your extension also increases
>>the convenience for you the developer and the users.
>>As a developer you're no longer tied to PHP's release
>>schedule, but you are free to release a new version whenever
>>you want. For the users of your extension it means, they can
>>have an updated version (be it a bug- or security-fix) anytime
>>you release it and not only when a PHP version comes out.
>>
>>Installing a PECL based extension is as easy as
>>$ pear install foobar
>>
>>See http://pecl.php.net/ for more information.
>>
>>Jan
>>--
>>GPG Key: BB96 56B0
>>Q: Thank Jan? - A: http://geschenke.an.dasmoped.net/
>>--[PinePGP]-----------------------------------------------------------
>>gpg: WARNING: using insecure memory!
>>gpg: please see http://www.gnupg.org/faq.html for more information
>>gpg: Signature made Sun 20 Jun 2004 11:05:40 AM PDT using DSA key ID BB9656B0
>>gpg: Good signature from "Jan Lehnardt <jan@dahlia.dasmoped.net>"
>>gpg:                 aka "Jan Lehnardt <jan@lehnardt.de>"
>>gpg:                 aka "Jan Lehnardt <jan@php.net>"
>>gpg:                 aka "Jan Lehnardt <jan@dasmoped.net>"
>>gpg: WARNING: This key is not certified with a trusted signature!
>>gpg:          There is no indication that the signature belongs to the owner.
>>Primary key fingerprint: 7BCC EB86 8313 DDA9 25DF  1805 ECA5 BCB7 BB96 56B0
>>--[PinePGP]----------------------------------------------------[end]--
>>
>
>

--
-----------------------------
Brad House
Sr. Developer
Main Street Softworks, Inc.

brad@mainstreetsoftworks.com
(386) 462-9522 Ext. 112
-----------------------------

Rasmus Lerdorf

22 years ago

On Sun, 20 Jun 2004, Brad House wrote:

> I was under the impression that it was one or the other, not
> both.  How do you coordinate the 2?

At distribution time we select which extensions to bundle.  Generally ones
we decide belong in the distribution tarball get a cvs symlink from
php-src to pecl just to make it easier to check out, but that isn't
required.

-Rasmus

Andi Gutmans

22 years ago

Actually I think the best way is to rename the directory in the repository
as it would save history.

At 10:36 AM 6/20/2004 -0400, Brad House wrote:

Edin Kadribasic

22 years ago

On Tuesday 22 June 2004 13:03, Andi Gutmans wrote:

> Actually I think the best way is to rename the directory in the repository
> as it would save history.

That would break the checkout of the older php versions. The directory needs
to be copied and then cvs delete the files in the old one.

Edin