Support for execution on Windows

[drtimf]

Since most of the implementation of this is platform independent (pulling images from repositories and extracting them), it should be possible to execute this on Windows. Currently the main problem is that paths being fed into the analyzers are in Windows form (i.e. backslash), while the analyzers are looking for key files using UNIX path separators.

Need to either have the analyzers look for paths using the native separator, or have the paths fed to the analyzers consistently use UNIX path separators.

I suppose the issue could be in the walker/tar.go where it is using a filepath.Clean() and filepath.Join() causing the native file separator to be used.

[avats-dev]

Can I work on this, is this still relevant? Also, can anyone guide me a bit in resolving this? Thanks.

[simar7]

Since most of the implementation of this is platform independent (pulling images from repositories and extracting them), it should be possible to execute this on Windows. Currently the main problem is that paths being fed into the analyzers are in Windows form (i.e. backslash), while the analyzers are looking for key files using UNIX path separators.

Do you have an example of what you saw here?

[avats-dev]

@simar7 I use ubuntu, but I used to use windows previously.

So, what I understood from the issue is that we can implement this in windows too, but we just have a problem that a file path such as file1/file2/.. would be like file1\file2\.. in windows. And, that's why I asked for help in how to implement this.

Is this clear?