Skip to content
Snippets Groups Projects
Commit 6559b2e7 authored by Sam Thursfield's avatar Sam Thursfield
Browse files

Log details of artifact splitting when building 'compose' elements

Artifact split rules are complicated to reason about. There needs to be
some way of seeing why a 'compose' artifact included a given file.

The log file now contains a long message like this, listing every
artifact, domain and file:

    [--:--:--] INFO    [initramfs/initramfs.bst]: Composed 2369 files

        Integration
          - var/cache/ldconfig/aux-cache

        gnu-toolchain/binutils.bst (not in any domain)
          - usr/x86_64-unknown-linux-gnu
          - usr/x86_64-unknown-linux-gnu/bin/ar
          - usr/x86_64-unknown-linux-gnu/bin/as
          - usr/x86_64-unknown-linux-gnu/bin/ld

        gnu-toolchain/make.bst (not in any domain)
          - usr
          - usr/lib
          - usr/share

        ...

Size of the log files is a concern and it may be that in future we
'compress' some of these entries, e.g. if all files in a given
directory come from one artifact then we just need to list the
directory, not every filename.
parent 0f134712
No related branches found
No related tags found
Loading
Pipeline #
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment