In data lunedì 27 giugno 2016 16:11:30, Paul Eggleton ha scritto:
> On Mon, 06 Jun 2016 15:27:17 Diego wrote:
> > Hi Oleksandr,
> >
> > In data venerdì 3 giugno 2016 20:56:32, Oleksandr Poznyak ha scritto:
> > > I found that that’s an issue with rpm packages. I didn't expect there
> > > might
> >
On Mon, 06 Jun 2016 15:27:17 Diego wrote:
> Hi Oleksandr,
>
> In data venerdì 3 giugno 2016 20:56:32, Oleksandr Poznyak ha scritto:
> > I found that that’s an issue with rpm packages. I didn't expect there
> > might
> > be some issue with rpm. If you really don't care which package management
> >
On Wed, Jun 8, 2016 at 1:58 AM, Oleksandr Poznyak
wrote:
> Hi, Edward.
> Your approach is valid. But RREPLACES is not enough.
>
> You should define that your package and original ones are conflicting and
> that it provides the same as original one for other packages.
>
> So in your recipe:
>
> RPR
Hi, Edward.
Your approach is valid. But RREPLACES is not enough.
You should define that your package and original ones are conflicting and
that it provides the same as original one for other packages.
So in your recipe:
RPROVIDES_${PN} = "sysvinit-inittab"
RREPLACES_${PN} = "sysvinit-inittab"
RC
On Tue, 07 Jun 2016 16:07:26 Edward Wingate wrote:
> On Tue, Jun 7, 2016 at 1:47 PM, Paul Eggleton
> wrote:
> > So what this will give you is alternative packages to be installed instead
> > of sysvinit-inittab in your image.
>
> I was under the (mistaken) impression that my recipe will run in
>
On Tue, Jun 7, 2016 at 1:47 PM, Paul Eggleton
wrote:
>
> So what this will give you is alternative packages to be installed instead of
> sysvinit-inittab in your image.
I was under the (mistaken) impression that my recipe will run in
addition to, not instead of, sysvinit-inittab (occurring after
On Tue, 07 Jun 2016 08:57:24 Edward Wingate wrote:
> On Tue, Jun 7, 2016 at 3:20 AM, Paul Eggleton
>
> wrote:
> > Let's clarify that for the benefit of others reading along - you
> > absolutely
> > *can* have multiple bbappends per recipe. To answer the original question
> > though, no you cannot
On Tue, Jun 7, 2016 at 3:20 AM, Paul Eggleton
wrote:
> Let's clarify that for the benefit of others reading along - you absolutely
> *can* have multiple bbappends per recipe. To answer the original question
> though, no you cannot have bbappends conditionally applied based on what image
> is being
Thanks, Paul. You are absolutely correct.
On Tue, Jun 7, 2016 at 1:20 PM, Paul Eggleton wrote:
> On Tue, 07 Jun 2016 00:10:58 Oleksandr Poznyak wrote:
> > Unfortunately You can't have two *.bbappend files per one package
> (recipe).
>
> Let's clarify that for the benefit of others reading along
On Tue, 07 Jun 2016 00:10:58 Oleksandr Poznyak wrote:
> Unfortunately You can't have two *.bbappend files per one package (recipe).
Let's clarify that for the benefit of others reading along - you absolutely
*can* have multiple bbappends per recipe. To answer the original question
though, no you
On Mon, Jun 6, 2016 at 3:06 PM, Edward Wingate wrote:
> It seems I cannot just append to inittab using the echo statements
> because /etc/inittab is not part of this recipe. Must I duplicate
> inittab first in my imageX-inittab.bb recipes?
I modified the recipes to include their own copy of initt
On Mon, Jun 6, 2016 at 2:10 PM, Oleksandr Poznyak
wrote:
> Hi,
> Unfortunately You can't have two *.bbappend files per one package (recipe).
>
> You can create two new recipes where You'll install what You need and plus
> add sysvinit-inittab to DEPENDS variable in those recipes. This will help to
Hi,
Unfortunately You can't have two *.bbappend files per one package (recipe).
You can create two new recipes where You'll install what You need and plus
add sysvinit-inittab to DEPENDS variable in those recipes. This will help
to retain the order of packages installation. Original sysvinit -> yo
On Wed, Jun 1, 2016 at 7:15 PM, Diego wrote:
>
> Hi Oleksandr,
>
> your approach is really interesting, but I'm unsure how to proceed with
> step 2) of your list.
>
> I've added the following in the bbappend:
>
> python do_package_prepend() {
> d.setVar('PACKAGES', "${PACKAGES} ${PN}-fstab-reg
Hi Oleksandr,
In data venerdì 3 giugno 2016 20:56:32, Oleksandr Poznyak ha scritto:
> I found that that’s an issue with rpm packages. I didn't expect there might
> be some issue with rpm. If you really don't care which package management
> system to use, switch to deb:
>
> PACKAGE_CLASSES = "pack
I found that that’s an issue with rpm packages. I didn't expect there might
be some issue with rpm. If you really don't care which package management
system to use, switch to deb:
PACKAGE_CLASSES = "package_deb"
On Fri, Jun 3, 2016 at 4:52 PM, Diego wrote:
> Hi Oleksandr,
>
> In data mercoledì
Hi Oleksandr,
In data mercoledì 1 giugno 2016 21:57:32, Oleksandr Poznyak ha scritto:
> Here is the content of bbappend recipe for base-files recipe:
>
> FILESEXTRAPATHS_append := "${THISDIR}/${PN}"
>
> SRC_URI += "file://fstab-flash \
> file://fstab-regular \
> "
>
> PACKAGES +
Here is the content of bbappend recipe for base-files recipe:
FILESEXTRAPATHS_append := "${THISDIR}/${PN}"
SRC_URI += "file://fstab-flash \
file://fstab-regular \
"
PACKAGES += " ${PN}-flash ${PN}-regular"
CONFFILES_${PN}-flash = "${CONFFILES_${PN}}"
CONFFILES_${PN}-regular = "${
In data mercoledì 1 giugno 2016 15:25:09, Oleksandr Poznyak ha scritto:
> Don't forget to add your fstab/inittab files into CONFFILES_${PN} cause if
> the package that includes them will be changed and You'll update it via
> package system, your POSTPROCESS hacks will be overwritten.
>
> Anyway, i
Don't forget to add your fstab/inittab files into CONFFILES_${PN} cause if
the package that includes them will be changed and You'll update it via
package system, your POSTPROCESS hacks will be overwritten.
Anyway, its better to avoid POSTPROCESS if possible.
1) Create *.bbappend recipe base-files
Hi Diego,
On Tue, 31 May 2016 18:05:19 Diego wrote:
> I've asked this question on IRC, but haven't received complete enough
> replies, so posting here.
>
> I have my own layer with my recipes and customizations. In my layer I have
> two images, one which is the "regular OS" that runs the product
Hi guys,
I've asked this question on IRC, but haven't received complete enough replies,
so posting here.
I have my own layer with my recipes and customizations. In my layer I have two
images, one which is the "regular OS" that runs the product application, and
one which is the "flash OS", a mi
22 matches
Mail list logo
