* packaging question
@ 2008-11-29 0:17 Dmitry Baryshkov
2008-11-29 16:13 ` Paul Sokolovsky
0 siblings, 1 reply; 4+ messages in thread
From: Dmitry Baryshkov @ 2008-11-29 0:17 UTC (permalink / raw)
To: openembedded-devel
Hi,
To make suspend work on tosa w/o problems, I have to put several files into
apm hooks directories. The question is: into which OE package should I put them?
--
With best wishes
Dmitry
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: packaging question
2008-11-29 0:17 packaging question Dmitry Baryshkov
@ 2008-11-29 16:13 ` Paul Sokolovsky
2008-12-03 0:11 ` Dmitry
0 siblings, 1 reply; 4+ messages in thread
From: Paul Sokolovsky @ 2008-11-29 16:13 UTC (permalink / raw)
To: openembedded-devel; +Cc: dbaryshkov, openembedded-devel
Hello,
On Sat, 29 Nov 2008 00:17:37 +0000 (UTC)
Dmitry Baryshkov <dbaryshkov@gmail.com> wrote:
> Hi,
>
> To make suspend work on tosa w/o problems, I have to put several
> files into apm hooks directories. The question is: into which OE
> package should I put them?
This was discussed well once - please put all machine- and device-
specific hacks and workarounds into separate package(s), to not
contaminate the main device-independent package with them, which would
either cast the main package machine-specific (QA nightmare), or affect
other devices unexpectedly (even bigger QA nightmare). There're few
examples of this idea already, see apm-wifi-suspendfix,
bluez-dtl1-workaround packages.
If such a package is machine specific, it's obvious where it should go
- into MACHINE_EXTRA_RDEPENDS. If it's however a workaround for
a particular device, especially pluggable, it makes sense to make it
more flexible and automagical and associate with the corresponding
kernel driver. See kernel.bbclass for how the packages above are
handled.
>
> --
> With best wishes
> Dmitry
[]
--
Best regards,
Paul mailto:pmiscml@gmail.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: packaging question
2008-11-29 16:13 ` Paul Sokolovsky
@ 2008-12-03 0:11 ` Dmitry
2008-12-03 6:53 ` Koen Kooi
0 siblings, 1 reply; 4+ messages in thread
From: Dmitry @ 2008-12-03 0:11 UTC (permalink / raw)
To: Paul Sokolovsky; +Cc: openembedded-devel, openembedded-devel
2008/11/29 Paul Sokolovsky <pmiscml@gmail.com>:
> Hello,
>
> On Sat, 29 Nov 2008 00:17:37 +0000 (UTC)
> Dmitry Baryshkov <dbaryshkov@gmail.com> wrote:
>
>> Hi,
>>
>> To make suspend work on tosa w/o problems, I have to put several
>> files into apm hooks directories. The question is: into which OE
>> package should I put them?
>
> This was discussed well once - please put all machine- and device-
> specific hacks and workarounds into separate package(s), to not
> contaminate the main device-independent package with them, which would
> either cast the main package machine-specific (QA nightmare), or affect
> other devices unexpectedly (even bigger QA nightmare). There're few
> examples of this idea already, see apm-wifi-suspendfix,
> bluez-dtl1-workaround packages.
>
> If such a package is machine specific, it's obvious where it should go
> - into MACHINE_EXTRA_RDEPENDS. If it's however a workaround for
> a particular device, especially pluggable, it makes sense to make it
> more flexible and automagical and associate with the corresponding
> kernel driver. See kernel.bbclass for how the packages above are
> handled.
Should I also bump PR of task-base after changing MACHINE_EXTRA_RRECOMMENDS?
>
>>
>> --
>> With best wishes
>> Dmitry
>
> []
>
> --
> Best regards,
> Paul mailto:pmiscml@gmail.com
>
--
With best wishes
Dmitry
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: packaging question
2008-12-03 0:11 ` Dmitry
@ 2008-12-03 6:53 ` Koen Kooi
0 siblings, 0 replies; 4+ messages in thread
From: Koen Kooi @ 2008-12-03 6:53 UTC (permalink / raw)
To: openembedded-devel
On 03-12-08 01:11, Dmitry wrote:
> 2008/11/29 Paul Sokolovsky<pmiscml@gmail.com>:
>> Hello,
>>
>> On Sat, 29 Nov 2008 00:17:37 +0000 (UTC)
>> Dmitry Baryshkov<dbaryshkov@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> To make suspend work on tosa w/o problems, I have to put several
>>> files into apm hooks directories. The question is: into which OE
>>> package should I put them?
>> This was discussed well once - please put all machine- and device-
>> specific hacks and workarounds into separate package(s), to not
>> contaminate the main device-independent package with them, which would
>> either cast the main package machine-specific (QA nightmare), or affect
>> other devices unexpectedly (even bigger QA nightmare). There're few
>> examples of this idea already, see apm-wifi-suspendfix,
>> bluez-dtl1-workaround packages.
>>
>> If such a package is machine specific, it's obvious where it should go
>> - into MACHINE_EXTRA_RDEPENDS. If it's however a workaround for
>> a particular device, especially pluggable, it makes sense to make it
>> more flexible and automagical and associate with the corresponding
>> kernel driver. See kernel.bbclass for how the packages above are
>> handled.
>
> Should I also bump PR of task-base after changing MACHINE_EXTRA_RRECOMMENDS?
and task-boot where appropriate.
regards,
Koen
>
>>> --
>>> With best wishes
>>> Dmitry
>> []
>>
>> --
>> Best regards,
>> Paul mailto:pmiscml@gmail.com
>>
>
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-12-03 6:56 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-11-29 0:17 packaging question Dmitry Baryshkov
2008-11-29 16:13 ` Paul Sokolovsky
2008-12-03 0:11 ` Dmitry
2008-12-03 6:53 ` Koen Kooi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox