From: Dmitry <dbaryshkov@gmail.com>
To: "Paul Sokolovsky" <pmiscml@gmail.com>
Cc: openembedded-devel@openembedded.org,
openembedded-devel@lists.openembedded.org
Subject: Re: packaging question
Date: Wed, 3 Dec 2008 03:11:19 +0300 [thread overview]
Message-ID: <bc64b4640812021611y34db8237vb1c286de035b99bc@mail.gmail.com> (raw)
In-Reply-To: <20081129181339.7152fdd4@widy.localdomain>
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
next prev parent reply other threads:[~2008-12-03 0:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 0:17 packaging question Dmitry Baryshkov
2008-11-29 16:13 ` Paul Sokolovsky
2008-12-03 0:11 ` Dmitry [this message]
2008-12-03 6:53 ` Koen Kooi
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=bc64b4640812021611y34db8237vb1c286de035b99bc@mail.gmail.com \
--to=dbaryshkov@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
--cc=pmiscml@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox