php-general Digest 5 Jul 2009 20:50:56 -0000 Issue 6213
Topics (messages 294896 through 294902):
Re: Editing PEAR packages
294896 by: Shawn McKenzie
294897 by: Greg Beaver
294899 by: Waynn Lue
294900 by: Greg Beaver
64 bit binary ?
294898 by: loki
294902 by: Daniel Brown
best way to properly build an include path *regardless* from where I am calling
the include?
294901 by: Govinda
Administrivia:
To subscribe to the digest, e-mail:
[email protected]
To unsubscribe from the digest, e-mail:
[email protected]
To post to the list, e-mail:
[email protected]
----------------------------------------------------------------------
--- Begin Message ---
Waynn Lue wrote:
> I wanted to makes some local edits to a PEAR package that I downloaded in
> order to build some custom functionality into it. What's the best way to
> manage this process to ensure that I don't accidentally blow away any
> changes if I update the package? Should I just copy the entire package to
> my own source repository, then use that directly instead of the PEAR
> package? And if I do it that way, is there an easy path to upgrade it?
>
> Waynn
>
You might want to see if you can just extend the classes to get the
functionality you want. You can override vars and methods from the base
class in your own class.
--
Thanks!
-Shawn
http://www.spidean.com
--- End Message ---
--- Begin Message ---
Waynn Lue wrote:
> I wanted to makes some local edits to a PEAR package that I downloaded in
> order to build some custom functionality into it. What's the best way to
> manage this process to ensure that I don't accidentally blow away any
> changes if I update the package? Should I just copy the entire package to
> my own source repository, then use that directly instead of the PEAR
> package? And if I do it that way, is there an easy path to upgrade it?
Best would be to follow Shawn's suggestion. If you do need to make
changes, you should contribute them back to the package, PEAR is an open
public repository, it may be incorporated and help others in your
situation as well (this is the point of PEAR and of open source).
Greg
--- End Message ---
--- Begin Message ---
Yeah, that's why I was hoping to maintain a separate install, since it
would be easier to diff the patches.
Shawn: Thanks for the suggestion to extend, I only wanted to make
small changes to an existing function though, so it's harder to do it
that way. My other thought was to refactor the underlying code base to
make it easier.
Waynn
On 7/5/09, Greg Beaver <[email protected]> wrote:
> Waynn Lue wrote:
>> I wanted to makes some local edits to a PEAR package that I downloaded in
>> order to build some custom functionality into it. What's the best way to
>> manage this process to ensure that I don't accidentally blow away any
>> changes if I update the package? Should I just copy the entire package to
>> my own source repository, then use that directly instead of the PEAR
>> package? And if I do it that way, is there an easy path to upgrade it?
>
> Best would be to follow Shawn's suggestion. If you do need to make
> changes, you should contribute them back to the package, PEAR is an open
> public repository, it may be incorporated and help others in your
> situation as well (this is the point of PEAR and of open source).
>
> Greg
>
--- End Message ---
--- Begin Message ---
Waynn Lue wrote:
> Yeah, that's why I was hoping to maintain a separate install, since it
> would be easier to diff the patches.
>
> Shawn: Thanks for the suggestion to extend, I only wanted to make
> small changes to an existing function though, so it's harder to do it
> that way. My other thought was to refactor the underlying code base to
> make it easier.
Hi Wayne,
If you're only making changes to one function, then you should extend
the class, and override the function. If the changes are extensive,
then check out the CVS repository, apply your changes, and use the "cvs
diff -u" command to create a patch to send back to the maintainer of the
package.
Greg
--- End Message ---
--- Begin Message ---
Hello
Is it plane to release 64 bit binary for php on windows ?
--
Stéphane
Http://www.arkadia.com/fra/
Http://www.arkadia.com/usa/
Http://www.arkadia.com/rus/
--- End Message ---
--- Begin Message ---
On Sun, Jul 5, 2009 at 15:43, loki<[email protected]> wrote:
> Hello
>
> Is it plane to release 64 bit binary for php on windows ?
Pierre?
--
</Daniel P. Brown>
[email protected] || [email protected]
http://www.parasane.net/ || http://www.pilotpig.net/
Check out our great hosting and dedicated server deals at
http://twitter.com/pilotpig
--- End Message ---
--- Begin Message ---
I am confusing myself reading the docs just now.
i.e.:
include_path
basename()
and dirname()
I had thought from many months ago that
<?php include '/somedir/somefile.php'; ?>
would include
somefile.php
living in
somedir
regardless from where in the site structure I am calling it.
Now it does not seem to be doing that.
What is the safest (portable) way to properly build an include path
*regardless* from where in my site I am calling the include?
If I understand right I can put includes in a dir/ specified by the
include_path setting, but I also want to know how to do this from just
within the root of my virtual server.
-Govinda
--- End Message ---
