Hello, I'm sorry for the late reply - I'm not sure how I didn't see this mail until now.
About having the DATABASE_URL in toaster.conf, I feel that this would break the separation between core bitbake and Django environments - toaster.conf is designed to be read and used by the bitbake core. As such, changing the value of this variable in toaster.conf will invalidate task signatures and caches of tasks, even if the value itself is irrelevant to the build task execution processes. This is likely to confuse users and trigger problems with cache reuse. More code would need to be added to bitbake to make this variable transparent to the build process. This being said, I'm not sure about the use case you have in mind - can you please give me more details on why this would be useful ? Alex On Fri, May 30, 2014 at 8:20 PM, Lerner, Dave <[email protected]> wrote: > Hi Alex, > > In your latest 20140650-bldcontrol push, you include a simpler model to > specify a global database path via a shell variable, DATABASE_URL. If set, > the variable is parsed in settings.py, overriding the simple > $pwd/toaster.sqlite, ... values. It works great for me. > > What do you think of reading DATABASE_URL, if present, from > conf/toaster.conf? > > That value would override the shell variable value if both are present? > If neither the toaster.conf:DATABASE_URL nor the shell variable > DATABASE_URL exist, then it defaults as it does now. > > Thanks, > Dave Lerner > -- Alex Damian Yocto Project SSG / OTC
-- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
