Option for retrieving parsed/inserted files

[Underrout]

This is kinda long term, but it would be potentially useful for me and others working on build systems if asar had an option for letting you retrieve a list of files it parsed/inserted after patching in order to track those files and changes to them to determine if things need to be reinserted. I mainly mean things like incsrc/incbin, but anything else like canreadfile1, filesize, etc. are also relevant, since changing those files, moving them, etc. can make a difference with those as well.

Basically it'd be nice to be able to get a list of all files that could change the result of attempting to insert the passed patch to determine if reinsertion might be prudent.

[trillllian]

definitely something we could add. a new api function that returns a list of all touched files shouldn't be too hard to add, we already have a virtual filesystem abstraction, can just hook it into that. the vfs also converts paths to absolute (though it has some issues with that.....) so i think it'd be easiest to return absolute paths from that api aswell

[p4plus2]

How should files inserted multiple times be handled?

[Underrout]

For my purposes just listing every file that's inserted at all once would be good enough, but if you wanna be very fancy about it you could not just list files, but also what about them was actually accessed (just the status of the file, byte offsets, character offsets, etc.). Could be useful if a build system actually caches files and can determine that the old and new file don't differ in the specific way they would have to in order to be necessarily reapplied, but that's probably overkill and not something I would likely use myself since there's also overhead in that.