William, It seems likely that since the change to scanning behavior will likely change many builds (as it's more accurate in tracing dependencies).
As such I think we should pre-announce it. Is it safe to say this change "breaks compatibility"? (If you ran a build to completion without change, and reran it you'd get a new build, switch to this change and it may rebuild some files) -Bill On Tue, Jul 28, 2015 at 12:16 AM, William Blevins <wblevins...@gmail.com> wrote: > Once we have finalized the patch, so that the behavioral changes can be > concretely defined, I will update those two files or should we do a > pre-release announcement like with the slots changes? > > V/R, > William > > On Mon, Jul 27, 2015 at 8:34 PM, Bill Deegan <b...@baddogconsulting.com> > wrote: > >> William, >> >> I just got around to doing a thorough read of your pull request and added >> a couple comments. >> >> Notably c++ doe (in the standard) support and require usage of header >> files with no extension: >> http://en.cppreference.com/w/cpp/header >> >> Another item is that since this is a change in functionality, >> documentation will need updates. >> And we should probably put a section in the src/CHANGES.txt and >> src/RELEASE.txt >> >> -Bill >> >> On Thu, Jul 9, 2015 at 7:18 AM, William Blevins <wblevins...@gmail.com> >> wrote: >> >>> >>> >>> On Thu, Jul 9, 2015 at 5:56 AM, Russel Winder <rus...@winder.org.uk> >>> wrote: >>> >>>> <Likely going off-topic…> >>>> >>>> On Thu, 2015-07-09 at 00:20 -0400, William Blevins wrote: >>>> > Thanks for responding everyone. I just wanted a "heart beat" so to >>>> > speak, >>>> >>>> You could always play the start of Dark Side of the Moon ;-) >>>> >>>> > since I wasn't sure how many members were watching the devs list. >>>> > I'm not >>>> > asking anyone to stop what they are doing, but a lot of what I have >>>> > left is >>>> > requirements related questions. >>>> >>>> Whilst I note every email, I mostly delete and move on due to not >>>> having enough time to properly contribute. >>>> >>>> > I will hopefully still be able to work on SCons after early >>>> > September, but >>>> > I am going to be a little disorganized during the move and culture >>>> > adjustment. I will be overseas for a year getting my MSc in Great >>>> > Britain. >>>> >>>> Just to note that Great Britain is a geographic but not political >>>> entity, something the ISO committees handing out country codes chose to >>>> forget when trying to solve the UK/Ukraine problem. >>>> >>>> Where will you be studying and living when here? >>>> >>> >>> University of Sussex in Brighton; approximately Sept 2015 - Sept 2016. >>> >>> >>>> >>>> > Also, I may not have my high-end workstation. I'm still debating >>>> > whether or >>>> > not I want to break it down and ship it. >>>> >>>> I guess this depends on cost. It always seems that countries shipping >>>> to UK pay about 0.5 or 0.3 the cost of shipping the same from the UK. >>>> Basically all companies (especially USA ones) charge far more in the UK >>>> for everything than they charge anywhere else in the world. >>>> >>> >>> Cost plus risk of it getting damaged. I generally build my own >>> workstations, so it's not like shipping X-U server form-factored machines. >>> I will have to dismantle it prior to shipping. I'm tempted to ship it case >>> less and buy another one in Britain because it'll be cheaper than shipping >>> (probably). >>> >>> >>>> >>>> -- >>>> Russel. >>>> >>>> ============================================================================= >>>> Dr Russel Winder t: +44 20 7585 2200 voip: >>>> sip:russel.win...@ekiga.net >>>> 41 Buckmaster Road m: +44 7770 465 077 xmpp: rus...@winder.org.uk >>>> London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder >>>> >>>> _______________________________________________ >>>> Scons-dev mailing list >>>> Scons-dev@scons.org >>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>>> >>>> >>> >>> _______________________________________________ >>> Scons-dev mailing list >>> Scons-dev@scons.org >>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>> >>> >> >> _______________________________________________ >> Scons-dev mailing list >> Scons-dev@scons.org >> https://pairlist2.pair.net/mailman/listinfo/scons-dev >> >> > > _______________________________________________ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > >
_______________________________________________ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev