Re: Split cons code (was: Re: Debian package and development of CONS)
[email protected] Fri, 5 Sep 2003 16:42:15 -0700
| Newsgroups | gmane.comp.gnu.cons.general |
|---|---|
| Message-ID | <OF2134E206.C856B813-ON86256D98.00808E08-88256D98.00823500@diamond.philips.com> |
This is a multipart message in MIME format. --===============0606145985== Content-Type: multipart/alternative; boundary="=_alternative 008234FD88256D98_=" This is a multipart message in MIME format. --=_alternative 008234FD88256D98_= Content-Type: text/plain; charset="us-ascii" Thank you for that clarification. That is not the problem I solved. I had very little experience with Cons prior to 2.3.0, as one of my first assignments was to upgrade our initial prototype of using Cons to 2.3.0. We do have the problem that you identify, and it is a problem in that many developers use DevStudio to build, but our official build is Cons and they must use that. I knew, and have informed them that outside contamination by other build systems requires a clean build in the Cons environment. But, I didn't make a big deal of this because Make, and I'm sure DevStudio would have the same problem. I apologize for leading you astray as to having a fix, --- Rick Croote Johan Holmberg <[email protected]> Sent by: [email protected] 09/05/2003 08:01 AM To: [email protected] cc: (bcc: Rick Croote/ATL-BTL/MS/PHILIPS) Subject: Re: Split cons code (was: Re: Debian package and development of CONS) Classification: On Fri, 5 Sep 2003 [email protected] wrote: > > On Sept. 6, 2002, I submitted a message to this group that included source > that has since fixed my dependency problems with the Command method. We > have been using Cons 2.3.0 and we are very happy with the performance and > reliability. > --- > Rick Croote > Are we really talking about the same thing ? Does your patched version work better than like below ? (I tried to apply your patch, but couldn't notice any difference in this situation). Suppose you have a Construct file like: $e = cons->new(); $e->Command("tgt.txt", "src.txt", "cp %< %>"); And issue the following commands: $ echo "qwerty" > src.txt $ cons . cp src.txt tgt.txt $ cp /dev/null tgt.txt $ cons . cons.pl: "." is up-to-date. <----- should NOT be up-to-date Note that this is just a "as small as possible" example. As far as I know it is not specific to "Command", but a general problem in 2.3.0 an later (even with your patch). I would be glad to be proven wrong ... /Johan Holmberg _______________________________________________ [email protected] http://mail.gnu.org/mailman/listinfo/cons-discuss Cons URL: http://www.dsmit.com/cons/ --=_alternative 008234FD88256D98_= Content-Type: text/html; charset="us-ascii" <br><font size=2 face="sans-serif">Thank you for that clarification. That is not the problem I solved. I had very little experience with Cons prior to 2.3.0, as one of my first assignments was to upgrade our initial prototype of using Cons to 2.3.0. We do have the problem that you identify, and it is a problem in that many developers use DevStudio to build, but our official build is Cons and they must use that. I knew, and have informed them that outside contamination by other build systems requires a clean build in the Cons environment. But, I didn't make a big deal of this because Make, and I'm sure DevStudio would have the same problem.</font> <br> <br><font size=2 face="sans-serif">I apologize for leading you astray as to having a fix,</font> <br><font size=2 face="sans-serif">---</font> <br><font size=2 face="sans-serif">Rick Croote</font> <br> <br> <br> <br> <table width=100%> <tr valign=top> <td> <td> <br> <br> <br> <br> <br><font size=1 face="sans-serif"><b>Johan Holmberg <[email protected]></b></font> <p><font size=1 face="sans-serif">Sent by: </font> <br><font size=1 face="sans-serif">[email protected]</font> <p><font size=1 face="sans-serif">09/05/2003 08:01 AM</font> <br> <td><font size=1 face="Arial"> </font> <br><font size=1 face="sans-serif"> To: [email protected]</font> <br><font size=1 face="sans-serif"> cc: (bcc: Rick Croote/ATL-BTL/MS/PHILIPS)</font> <br><font size=1 face="sans-serif"> Subject: Re: Split cons code (was: Re: Debian package and development of CONS)</font> <p><font size=1 face="sans-serif"> Classification: </font> <br></table> <br> <br> <br><font size=2 face="Courier New"><br> On Fri, 5 Sep 2003 [email protected] wrote:<br> ><br> > On Sept. 6, 2002, I submitted a message to this group that included source<br> > that has since fixed my dependency problems with the Command method. We<br> > have been using Cons 2.3.0 and we are very happy with the performance and<br> > reliability.<br> > ---<br> > Rick Croote<br> ><br> <br> Are we really talking about the same thing ?<br> <br> Does your patched version work better than like below ? (I tried to<br> apply your patch, but couldn't notice any difference in this<br> situation).<br> <br> Suppose you have a Construct file like:<br> <br> $e = cons->new();<br> $e->Command("tgt.txt", "src.txt", "cp %< %>");<br> <br> And issue the following commands:<br> <br> $ echo "qwerty" > src.txt<br> $ cons .<br> cp src.txt tgt.txt<br> $ cp /dev/null tgt.txt<br> $ cons .<br> cons.pl: "." is up-to-date. <----- should NOT be up-to-date<br> <br> <br> Note that this is just a "as small as possible" example. As far as I<br> know it is not specific to "Command", but a general problem in 2.3.0<br> an later (even with your patch).<br> <br> I would be glad to be proven wrong ...<br> <br> /Johan Holmberg<br> <br> <br> <br> _______________________________________________<br> [email protected]<br> http://mail.gnu.org/mailman/listinfo/cons-discuss<br> Cons URL: http://www.dsmit.com/cons/<br> </font> <br> <br> --=_alternative 008234FD88256D98_=-- --===============0606145985== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ [email protected] http://mail.gnu.org/mailman/listinfo/cons-discuss Cons URL: http://www.dsmit.com/cons/ --===============0606145985==--