[Toaster] [RFC] Handling IMAGE_INSTALL_append
Reyna, David
david.reyna at windriver.com
Wed Mar 4 07:58:34 PST 2015
Yes I will take this defect.
David
Sent from my iPhone
> On Mar 4, 2015, at 4:14 AM, Barros Pena, Belen <belen.barros.pena at intel.com> wrote:
>
>
>
> On 04/03/2015 11:46, "Damian, Alexandru" <alexandru.damian at intel.com>
> wrote:
>
>> This needs to be done in the backend - we can't trust whatever the
>> browser is telling us, we have to check it on the server side.
>
> Thanks, Alex. If nobody fundamentally disagrees, can I go ahead and open a
> Bugzilla entry for this?
>
> David: can I assign it to you?
>
> Cheers
>
> Belén
>
>>
>>
>> Alex
>>
>>
>>
>> On Wed, Mar 4, 2015 at 10:38 AM, Barros Pena, Belen
>> <belen.barros.pena at intel.com> wrote:
>>
>> So what do you guys think?
>>
>> Thanks!
>>
>> Belén
>>
>> On 04/03/2015 00:32, "Reyna, David" <david.reyna at windriver.com> wrote:
>>
>>>> From my perspective, option 1 is the best one.
>>>
>>> And I still agree with that.
>>>
>>> Trying to have the user do this opens the door to trivial but blocking
>>> defects, and the GUI experience is supposed to be superior and more
>>> guided than the raw command line experience.
>>>
>>> The fall back is to have the front end interface enforce this invisibly,
>>> in other words always force a leading space when it writes this value to
>>> the backend but present/accept a trimmed value. This is something that
>>> could be done quickly, but then we are spreading this arcane syntax rule
>>> to the frontend away from the presumably more intelligent backend.
>>>
>>> - David
>>>
>>>> -----Original Message-----
>>>> From: toaster-bounces at yoctoproject.org [mailto:toaster-
>>>> bounces at yoctoproject.org] On Behalf Of Barros Pena, Belen
>>>> Sent: Tuesday, March 03, 2015 2:47 AM
>>>> To: toaster at yoctoproject.org
>>>> Subject: [Toaster] [RFC] Handling IMAGE_INSTALL_append
>>>>
>>>> The default project configuration we ship with Toaster includes the
>>>> IMAGE_INSTALL_append variable. This variable requires a space before
>>>> the
>>>> first package name. We have spoken before about taking 2 possible
>>>> approaches to handle this:
>>>>
>>>> 1. Toaster takes responsibility and adds the space for you. How this
>>>> could
>>>> be done, I am not sure. I guess we can either somehow identify
>>>> IMAGE_INSTALL_append as the type of variable that requires a space
>>>> before
>>>> the first list item, or we can hardcode it.
>>>>
>>>> 2. Users take responsibility and add the space themselves. Easier to
>>>> implement (we add some help text to the field), but bound to fail
>>>> (users
>>>> don't read help text).
>>>>
>>>> From my perspective, option 1 is the best one. I don't care if we need
>>>> to
>>>> hardcode it. Adding this variable to the default project configuration
>>>> is
>>>> very much a temporary solution until we provide functionality to
>>>> customise
>>>> the list of packages installed by an image recipe.
>>>>
>>>> Would this be acceptable to everybody else?
>>>>
>>>> Thanks!
>>>>
>>>> Belén
>>>>
>>>> --
>>>> _______________________________________________
>>>> toaster mailing list
>>>> toaster at yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/toaster
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> Alex Damian
>> Yocto Project
>>
>> SSG / OTC
>
More information about the toaster
mailing list