Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Herve Codina <herve.codina@bootlin.com>,
	"Yann E. MORIN" <yann.morin.1998@free.fr>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/pkg-utils: only overwrite newer for per-package-rsync
Date: Sun, 24 Oct 2021 15:02:55 +0200	[thread overview]
Message-ID: <20211024150255.292cc135@windsurf> (raw)
In-Reply-To: <20211024052852.3999292-1-james.hilliard1@gmail.com>

Hello James,

On Sat, 23 Oct 2021 23:28:52 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:

> Currently during target-finalize we rsync packages in sorted order,
> however if one rebuilds a package that has reverse dependencies
> the rebuilt version may get overwritten by the old version from the
> reverse dependency if the reverse dependency gets recyned after
> the rebuilt package(based on alphabetical sorting) during the
> target-finalize stage.
> 
> To prevent this only copy files newer than their targets.
> 
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>

There's an entire patch series from Hervé Codina at
https://lore.kernel.org/buildroot/20210817083930.3718711-1-herve.codina@bootlin.com/
to address this issue, and it is much more involved. Parts of the
series have been applied, but not all of it, as there are some
remaining issues.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2021-10-24 13:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-24  5:28 [Buildroot] [PATCH 1/1] package/pkg-utils: only overwrite newer for per-package-rsync James Hilliard
2021-10-24 13:02 ` Thomas Petazzoni [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=20211024150255.292cc135@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=herve.codina@bootlin.com \
    --cc=james.hilliard1@gmail.com \
    --cc=yann.morin.1998@free.fr \
    /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