Le 16 août 07 à 09:57, source_changes@macosforge.org a écrit :
Revision 27925 Author jwa@macports.org Date 2007-08-16 00:57:10 -0700 (Thu, 16 Aug 2007) Log Messagea new port containing a development version of PHP5, currently 5.2.4RC1Added Paths trunk/dports/www/php5-devel/ trunk/dports/www/php5-devel/Portfile <snip>
For this port to be really useful, every port depending on port:php5 should depend on (path|lib):*:php5. -- Anthony Ramine, the infamous MacPorts Trac slave. nox@macports.org
N_Ox wrote:
For this port to be really useful, every port depending on port:php5 should depend on (path|lib):*:php5.
Can't you do the usual workaround, and installing the "php5" port deactivated to fill dependencies and then install the "php5-devel" port activated to get the new version ? Then again, relying on the current (buggy) behaviour might not be the best of ideas... It's one of the Olden Goldies: http://trac.macports.org/projects/macports/ticket/7361 Note that it is quite dangerous, if you install a port and then deactivate it then MacPorts will still think that the port is there and if you later on try to build something that requires the port - then it might as well link against a system library or other installation and if that happens to work (in that particular moon phase), no error is issued either. You can easilly get some hard to find bugs this way. Sometimes you get off easy, with a "library not found" error in the configure phase or a "image not found" when trying to run a binary... --anders
Le 16 août 07 à 10:56, Anders F Björklund a écrit :
N_Ox wrote:
For this port to be really useful, every port depending on port:php5 should depend on (path|lib):*:php5.
Can't you do the usual workaround, and installing the "php5" port deactivated to fill dependencies and then install the "php5-devel" port activated to get the new version ?
Then again, relying on the current (buggy) behaviour might not be the best of ideas... It's one of the Olden Goldies: http:// trac.macports.org/projects/macports/ticket/7361
Note that it is quite dangerous, if you install a port and then deactivate it then MacPorts will still think that the port is there and if you later on try to build something that requires the port - then it might as well link against a system library or other installation and if that happens to work (in that particular moon phase), no error is issued either. You can easilly get some hard to find bugs this way. Sometimes you get off easy, with a "library not found" error in the configure phase or a "image not found" when trying to run a binary...
--anders
I hate workarounds =). -- Anthony Ramine, the infamous MacPorts Trac slave. nox@macports.org
On 16.8.2007, at 11.06, N_Ox wrote:
For this port to be really useful, every port depending on port:php5 should depend on (path|lib):*:php5.
A devel port is not intended to be really useful, at least I think the purpose of this port, like all devel ports, is to check things out, its purpose is not to be very dependable, because it is bound to change, maybe a lot. So it would be nice, if this port could be useful, but I'm afraid it will never be really useful… ! ! Jyrki Wahlstedt ! http://www.wahlstedt.fi/jyrki/ ! ! Our life is no dream; but it ought to become one and perhaps will. ! PGP key ID: 0x139CC386 fingerprint: F355 B46F 026C B8C1 89C0 A780 6366 EFD9 139C C386
participants (3)
-
Anders F Björklund
-
Jyrki Wahlstedt
-
N_Ox