Deletion of files not present in config about update4j HOT 8 CLOSED

from update4j.

Hello, thanks for your kind words.

In a typical case where a single client hasn't updated across a few versions the solution is simply to use it cached (offline) version of their current config as the delete source.

The deleteOldFiles wasn't designed to delete arbitrary files, but instead focuses on files left over from old versions. Being that the user did not update, those middle version files aren't even present there.

Is there a case where this doesn't work for you?

from update4j.

Do you have a code example for using the cached offline version of their config file? That would pretty much do what I would like it to :)
Deletion of other, unknown files would only be a plus point, which is not that important right now

from update4j.

The default bootstrap does just this

In general, you would want to have the config saved locally so if the user is offline they can still start the application. Unless if you only use update4j for updating and not for launching, in which case caching isn't important at all.

from update4j.

Thank you again for your help!
Unfortunately, I am not able to locate the config.old file on my system.

This is what I am doing right now, I added some code from the DefaultBootstrap. Any Idea why there is no config.old file?

        InputStreamReader in = new InputStreamReader(connection.getInputStream());
        Configuration config = Configuration.read(in);
        
        if (config.requiresUpdate()) {
            Path path = Paths.get(System.getProperty("user.home") + "/update.zip");
            ArchiveUpdateOptions archiveOptions = UpdateOptions.archive(path);
            config.update(archiveOptions);
            Archive archive = Archive.read(System.getProperty("user.home") + "/update.zip");
            Configuration oldConfig = null;
        
            try (FileSystem fs = archive.openConnection()) {
	            Path oldPath = fs.getPath("config.old");
	            if (Files.exists(oldPath)) {
		            try (BufferedReader in2 = Files.newBufferedReader(oldPath)) {
			            oldConfig = Configuration.read(in2);
		            }
	            }
            }
        
            archive.install();
            config.deleteOldFiles(oldConfig);
        }
        
        config.launch();

from update4j.

This isn't part of the default archive format, but added by the default bootstrap

This was left as part of userland setup being unopinionated where and how to keep configs between updates.

from update4j.

facepalm
So basically after the first update the local config is created. For all further updates, the config is read and updated.
Thank you so much! Hopefuly I won't have to bother you again for some time ;)

from update4j.

Glad I could help!

from update4j.