public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Stephen Ecker <stephenecker240@gmail.com>
To: Uladzimir Bely <ubely@ilbers.de>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: make sure a package builds last
Date: Wed, 29 Jan 2025 09:17:42 -0600	[thread overview]
Message-ID: <CAK9C7GBmAUWhqGpf+Jb8KLAUxPKeEWTjLOQ=HaahEZBv4pi7xQ@mail.gmail.com> (raw)
In-Reply-To: <d3be7d2fac4c79c1ceb8943f6afae8bb6e8c5bec.camel@ilbers.de>

[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]

I just need one dpkg-raw recipe to build after all the other
dpkg-recipes... It seems like this should work, but it doesn't:

DEPENDS = "other dpkg recipes"

do_prepare_build[recrdeptask] = "do_dpkg_publish"

It still runs in parallel

On Wed, Jan 29, 2025, 2:20 AM Uladzimir Bely <ubely@ilbers.de> wrote:

> On Tue, 2025-01-28 at 04:49 -0800, Stephen Ecker wrote:
> > how can I ensure that a dpkg-raw package is built _last_, after all
> > other packages have been built?  preferably before the base image is
> > built, but that's not entirely necessary.
> >
> > thanks
>
> Bitbake tends to run tasks in parallel as soon as they don't depend on
> any other tasks. Any attempt to change this behavior would be probably
> tricky and cause longer build time, I guess.
>
>
> > --
> > You received this message because you are subscribed to the Google
> > Groups "isar-users" group.
> > To unsubscribe from this group and stop receiving emails from it,
> > send an email to isar-users+unsubscribe@googlegroups.com.
> > To view this discussion visit
> >
> https://groups.google.com/d/msgid/isar-users/73a37c33-3c21-4080-8a50-bac81772fc29n%40googlegroups.com
> > .
>
> --
> Best regards,
> Uladzimir.
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/CAK9C7GBmAUWhqGpf%2BJb8KLAUxPKeEWTjLOQ%3DHaahEZBv4pi7xQ%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 2695 bytes --]

      reply	other threads:[~2025-01-29 15:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-28 12:49 Stephen Ecker
2025-01-29  8:20 ` Uladzimir Bely
2025-01-29 15:17   ` Stephen Ecker [this message]

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='CAK9C7GBmAUWhqGpf+Jb8KLAUxPKeEWTjLOQ=HaahEZBv4pi7xQ@mail.gmail.com' \
    --to=stephenecker240@gmail.com \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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