Skip to content

support: limit install-time instrumentation to current package's files (branch yem/files-list-2)

Yann E. MORIN buildroot 1 version New

Get series with b4
b4 am 20190109181001.GL4022@scaer

Versions newest first

  1. v1 Latest0 of 19 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 19 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [Buildroot] [PATCH 00/19] support: limit install-time instrumentation to current package's files (branch yem/files-list-2)

Thomas, All,

On 2019-01-09 14:39 +0100, Thomas De Schampheleire spake thusly:

Quoted 2 lines

El mar., 8 ene. 2019 a las 22:30, Yann E. MORIN
(<[email protected]>) escribi?:

[--SNIP--]

Quoted 16 lines
Quoted 6 lines

But for a more generic solution, we'd need a way to detect files that were not previously present but now are.

So we'd need to maintain a list of files from before the installation and another for after the installation. And oh wait, isn't that basically what we previously did (modulo the md5)? ;-)

Without md5sum, there is only a find before and after each package installation, which shouldn't take long.

The md5 is only necessary if you care about changing existing files. And normally, if you change existing files, their timestamp will be updated, so your solution with '-newer-than foo_before' should be fine. Only when you change files and still keep their old timestamps, would something be missed.

Quoted 3 lines

So, a possible solution could be a combination of the original 'find before+after' solution and your new 'newer-than foo_before' solution. Am I talking gibberish?

Now that I slept on it, detecting and fixing this problem appropriately is impossible, unless we re-instate the leading md5sum as well.

If you allow for a package to install a file in the past, how do you know that the file indeed did not previously exist?

That is, if the file did not previously exist, then comparing the list before/after would indeed detect it. However, if the file did previously exist, then your package would overwrite it *and* set it in the past, and then comparing the list before/after would not detect it.

And in either case, our find -newer would not detect it either.

So, the only way to properly account for this situation would be, guess what, to reinstate an md5sum before and after the installation and compare them file by file.

However, as we've seen, this is totally unacceptable.

So, I hereby declare that I think that I believe that in my opinion I can only think that a package which installs a file in the past is broken (or borked, as you may prefer). ;-)

Regards,
Yann E. MORIN.

Signature · 6 lines
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'