All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Damian, Alexandru" <alexandru.damian@intel.com>
Cc: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: Can DATABASE_URL also be read from toaster.conf
Date: Tue, 03 Jun 2014 14:26:16 +0100	[thread overview]
Message-ID: <1401801976.12440.91.camel@ted> (raw)
In-Reply-To: <CAJ2CSBtWLYCmSnYhLFBugK9kcn5XqF1TLjX4j=cmK_nmjBrAvg@mail.gmail.com>

On Tue, 2014-06-03 at 14:09 +0100, Damian, Alexandru wrote:
> 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.

Changing an incidental variable like this will trigger reparses and will
invalidate some caches but the task signatures themselves wouldn't
change due to it since they have no dependency on the variable.

I make no comment on whether its a good/bad idea, just want to ensure we
base the decisions on the right data.

Cheers,

Richard






      reply	other threads:[~2014-06-03 13:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-30 19:20 Can DATABASE_URL also be read from toaster.conf Lerner, Dave
2014-06-03 13:09 ` Damian, Alexandru
2014-06-03 13:26   ` Richard Purdie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1401801976.12440.91.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alexandru.damian@intel.com \
    --cc=toaster@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.