Re: RFC: Moving from confvars.sh to moz.configure

2016-05-05 Thread Christopher Manchester
On Thu, May 5, 2016 at 1:28 PM, Michael Shal wrote: > Are there particular issues with option 1 that we're trying to avoid? In > other words, have we had problems in the confvars.sh world that we need to > address? (Aside from converting .sh -> .py). > I found when doing conversions that having

Re: RFC: Moving from confvars.sh to moz.configure

2016-05-05 Thread Michael Shal
Are there particular issues with option 1 that we're trying to avoid? In other words, have we had problems in the confvars.sh world that we need to address? (Aside from converting .sh -> .py). Although there are aspects of option 2) that I like, I could also see something like toolkit/moz.configur

Re: RFC: Moving from confvars.sh to moz.configure

2016-05-04 Thread Gregory Szorc
On Tue, May 3, 2016 at 1:45 PM, Christopher Manchester < chmanches...@gmail.com> wrote: > We're moving some things currently defined in various confvars.sh files to > Python configure (moz.configure), and have reached a point where feedback > would be helpful, as we are replacing a relatively long

RFC: Moving from confvars.sh to moz.configure

2016-05-03 Thread Christopher Manchester
We're moving some things currently defined in various confvars.sh files to Python configure (moz.configure), and have reached a point where feedback would be helpful, as we are replacing a relatively longstanding thing, and many are likely to interact with these options in the future. The competin