# question on policy of renaming an extension - Thread: https://externals.io/message/10647 - Original archive: https://news-web.php.net/php.internals/10647 - Started by Brad House on 2004-06-20T15:19:59+00:00 - Messages: 11 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #10647 — Brad House — 2004-06-20T15:19:59+00:00 URL: https://externals.io/message/10647#10647 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 --- ## #10648 — Derick Rethans — 2004-06-20T15:25:47+00:00 URL: https://externals.io/message/10647#10648 · In reply to: #10647 > 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 --- ## #10649 — Brad House — 2004-06-20T15:36:01+00:00 URL: https://externals.io/message/10647#10649 · In reply to: #10648 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: > > > > > […] > > > 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 --- ## #10650 — Derick Rethans — 2004-06-20T15:48:21+00:00 URL: https://externals.io/message/10647#10650 · In reply to: #10649 > 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 --- ## #10655 — Jan Lehnardt — 2004-06-20T17:05:22+00:00 URL: https://externals.io/message/10647#10655 · In reply to: #10649 Hi, > 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/ --- ## #10656 — Brad House — 2004-06-20T17:42:22+00:00 URL: https://externals.io/message/10647#10656 · In reply to: #10655 > > 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 --- ## #10657 — Rasmus Lerdorf — 2004-06-20T17:50:03+00:00 URL: https://externals.io/message/10647#10657 · In reply to: #10656 > 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 --- ## #10658 — Jan Lehnardt — 2004-06-20T18:05:39+00:00 URL: https://externals.io/message/10647#10658 · In reply to: #10656 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, > 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 --- ## #10659 — Rasmus Lerdorf — 2004-06-20T18:08:36+00:00 URL: https://externals.io/message/10647#10659 · In reply to: #10658 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 > --[PinePGP]--------------------------------------------------[begin]-- > Hi, > > > […] > > 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 " > gpg: aka "Jan Lehnardt " > gpg: aka "Jan Lehnardt " > gpg: aka "Jan Lehnardt " > 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] --- ## #10664 — Brad House — 2004-06-20T18:59:10+00:00 URL: https://externals.io/message/10647#10664 · In reply to: #10659 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 > > > > > > […] > > -- ----------------------------- Brad House Sr. Developer Main Street Softworks, Inc. brad@mainstreetsoftworks.com (386) 462-9522 Ext. 112 --- ## #10665 — Rasmus Lerdorf — 2004-06-20T20:10:22+00:00 URL: https://externals.io/message/10647#10665 · In reply to: #10664 > 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