Can't do a "delta build" these days?

Ryan Gonzalez rymg19 at gmail.com
Fri Sep 6 03:33:34 UTC 2019


--force-clean only clears out the target build directory that you pass to
the CLI. All the build steps and downloads are cached elsewhere (in
`.flatpak-builder`, and if nothing needs to be changed, then
flatpak-builder will just check out the cached modules onto a fresh build
directory.

In short, afaik --force-clean shouldn't actually cause anything to be
rebuilt. (I do think the name can be a bit misleading...)

On Thu, Sep 5, 2019, 8:02 PM Daniel Kasak <d.j.kasak.dk at gmail.com> wrote:

> Hi all.
>
> I used to be able to run a build of a large project, which would only
> build things I'd changed, and optionally things where there are new
> git commits. I could disable the build of libs with new git commits
> with the --disable-updates switch.
>
> Some time recently, I started getting the error:
>  App dir 'appdir' is not empty. Please delete the existing contents or
> use --force-clean.
>
> I was under the impression that my 'appdir' never used to get cleared
> out. The --force-clean option removes all my downloaded tarballs, git
> repos, and built packages. So I can still build ... but I now have to
> build the entire project each time, which takes *ages*.
>
> Has something changed?
>
> Dan
> _______________________________________________
> Flatpak mailing list
> Flatpak at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/flatpak
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/flatpak/attachments/20190905/9bfc48f4/attachment.html>


More information about the Flatpak mailing list