Dummy calls of decker pollute the current directory

[salbeira]

Checking if decker is installed, checking the version or just accidentally running decker in any directory where the call does nothing causes decker to create a .decker directory.

This pollutes your directories - especially your home directory - with unneccesary (hidden) files and directories.

A call to decker, especially decker version should not leave behind any files if the directory wasn't a "decker directory" (with a decker.yaml).

[monofon]

Should be fixed.

[salbeira]

decker --help still pollutes directories:

hauer@bruce:~/foo$ ls -la
total 8
drwxrwxr-x  2 hauer hauer 4096 Mär  4 16:59 .
drwxr-xr-x 39 hauer hauer 4096 Mär  4 16:59 ..
hauer@bruce:~/foo$ decker --help
[...]
hauer@bruce:~/foo$ ls -la
total 12
drwxrwxr-x  3 hauer hauer 4096 Mär  4 17:00 .
drwxr-xr-x 39 hauer hauer 4096 Mär  4 16:59 ..
drwxrwxr-x  2 hauer hauer 4096 Mär  4 17:00 .decker

[monofon]

I moved the transient .decker dir to a random temporary location in 0203f2c.

Please check for problems.

[monofon]

@salbeira can you confirm?

• [ ] No more pollution
• [ ] No new problems
• [ ] Especially not on Windows

[salbeira]

I get an invalid argument error for the creation of the directory (I guess it is the colon after c23fea860C or the prefix \\\\?\\)

decker.exe: C:\Users\Hauer\AppData\Local\Temp\decker-c23fea860C:-Users-Hauer-test: CreateDirectory "\\\\?\\C:\\Users\\Hauer\\AppData\\Local\\Temp\\decker-c23fea860C:-Users-Hauer-test": invalid argument (The directory name is invalid.)

[salbeira]

I just found out that running decker anywhere where there is no decker.yaml file still produces a public directory with 512kb of data (a partially unpacked support directory) before the build fails.