From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Cc: Giulia Piu <giulia@closertag.com>
Subject: Re: Deleting layers in Hob
Date: Fri, 30 Mar 2012 13:19:15 +0100 [thread overview]
Message-ID: <2875706.c2lxvPnLMP@helios> (raw)
In-Reply-To: <CB9B56AE.BE8E%belen.barros.pena@intel.com>
On Friday 30 March 2012 11:26:15 Barros Pena, Belen wrote:
> On 30/03/2012 07:32, "Khem Raj" <raj.khem@gmail.com> wrote:
> >On Thu, Mar 29, 2012 at 4:05 AM, Barros Pena, Belen
> ><belen.barros.pena@intel.com> wrote:
> >> Do we have enough information to make a decision about the meta-yocto
> >> layer? I don't understand all the technical details, but I am inclined
> >> to make it non-deletable in Hob (i.e. it is not possible to delete this
> >> layer in Hob).
> >>
> >> What do you think?
> >
> >bad idea. Unless you intend to shackle hob to yocto. Is that the
> >intention ?
>
> Well: I don't know. Does anybody have an answer?
We don't want to tie hob to meta-yocto, no. The solution to this problem is to
have Hob understand when removing a layer is removing the DISTRO selection
that a user currently has made and warning them about it; if they respond in
affirmative then DISTRO can be set to empty (or we can allow them to select an
alternative, perhaps - something for the designers to consider). Fortunately
since DISTRO points directly to a file in conf/distro/ the detection part is
pretty easy to implement.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-03-30 12:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 6:48 Deleting layers in Hob Xu, Dongxiao
2012-03-27 7:19 ` Lu, Lianhao
2012-03-27 16:56 ` Joshua Lock
2012-03-29 11:05 ` Barros Pena, Belen
2012-03-29 12:00 ` Xu, Dongxiao
2012-03-29 15:47 ` Barros Pena, Belen
2012-03-30 6:32 ` Khem Raj
2012-03-30 11:26 ` Barros Pena, Belen
2012-03-30 12:19 ` Paul Eggleton [this message]
2012-04-02 10:48 ` Barros Pena, Belen
2012-04-02 10:55 ` Paul Eggleton
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=2875706.c2lxvPnLMP@helios \
--to=paul.eggleton@linux.intel.com \
--cc=giulia@closertag.com \
--cc=yocto@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.