Le 28 août 07 à 04:00, source_changes@macosforge.org a écrit :
Revision 28311 Author mww@macports.org
<snip/> + system "cd ${destroot}${prefix}/bin && ln -sf ${nprefix}/bin/gcc- apple-4.0 && ln -sf ${nprefix}/bin/cpp-apple-4.0" <snip/>
Why don't you use cd and ln TCL procedures? -- Anthony Ramine, the infamous MacPorts Trac slave. nox@macports.org
On Aug 28, 2007, at 1:58 PM, N_Ox wrote:
Le 28 août 07 à 04:00, source_changes@macosforge.org a écrit :
Revision 28311 Author mww@macports.org
<snip/> + system "cd ${destroot}${prefix}/bin && ln -sf ${nprefix}/bin/gcc- apple-4.0 && ln -sf ${nprefix}/bin/cpp-apple-4.0" <snip/>
Why don't you use cd and ln TCL procedures?
You shouldn't use Tcl's "cd" in a port -- it changes the current working directory of the entire process. We should probably remove the Tcl command from the interpreter. -landonf
Le 28 août 07 à 23:15, Landon Fuller a écrit :
On Aug 28, 2007, at 1:58 PM, N_Ox wrote:
Le 28 août 07 à 04:00, source_changes@macosforge.org a écrit :
Revision 28311 Author mww@macports.org
<snip/> + system "cd ${destroot}${prefix}/bin && ln -sf ${nprefix}/bin/ gcc-apple-4.0 && ln -sf ${nprefix}/bin/cpp-apple-4.0" <snip/>
Why don't you use cd and ln TCL procedures?
You shouldn't use Tcl's "cd" in a port -- it changes the current working directory of the entire process. We should probably remove the Tcl command from the interpreter.
-landonf
I think we should change this behavior rather than disabling the command. Useful working directories in build stages (e.g. ${worksrcpath} in configure or ${destroot} in destroot) would be a nice feat. -- Anthony Ramine, the infamous MacPorts Trac slave. nox@macports.org
On Aug 28, 2007, at 4:16 PM, N_Ox wrote:
You shouldn't use Tcl's "cd" in a port -- it changes the current working directory of the entire process. We should probably remove the Tcl command from the interpreter.
-landonf
I think we should change this behavior rather than disabling the command. Useful working directories in build stages (e.g. ${worksrcpath} in configure or ${destroot} in destroot) would be a nice feat.
We would have to rewrite? all file operations to take into account a virtual current working directory, and somehow maintain that context within the current execution block. Seems safer and less work to just not depend on a the current working directory (which is always a good idea, anyway).
Le 29 août 07 à 01:18, Landon Fuller a écrit :
On Aug 28, 2007, at 4:16 PM, N_Ox wrote:
You shouldn't use Tcl's "cd" in a port -- it changes the current working directory of the entire process. We should probably remove the Tcl command from the interpreter.
-landonf
I think we should change this behavior rather than disabling the command. Useful working directories in build stages (e.g. ${worksrcpath} in configure or ${destroot} in destroot) would be a nice feat.
We would have to rewrite? all file operations to take into account a virtual current working directory, and somehow maintain that context within the current execution block. Seems safer and less work to just not depend on a the current working directory (which is always a good idea, anyway).
So what is the purpose of the ln procedure? and mv? -- Anthony Ramine, the infamous MacPorts Trac slave. nox@macports.org
On Aug 28, 2007, at 10:30 PM, N_Ox wrote:
Le 29 août 07 à 01:18, Landon Fuller a écrit :
On Aug 28, 2007, at 4:16 PM, N_Ox wrote:
You shouldn't use Tcl's "cd" in a port -- it changes the current working directory of the entire process. We should probably remove the Tcl command from the interpreter.
-landonf
I think we should change this behavior rather than disabling the command. Useful working directories in build stages (e.g. ${worksrcpath} in configure or ${destroot} in destroot) would be a nice feat.
We would have to rewrite? all file operations to take into account a virtual current working directory, and somehow maintain that context within the current execution block. Seems safer and less work to just not depend on a the current working directory (which is always a good idea, anyway).
So what is the purpose of the ln procedure? and mv?
They will correctly operate on fully qualified paths.
participants (2)
-
Landon Fuller
-
N_Ox