Hi everyone, i have a question about the use of the compactor app...
I often use it with my apps, but i was wondering what happens when a compacted applications gets an update from te portableapps site...
Do the "compression" get lost?
I think this cause the "update" (if i'm not wrong) it's a new installation over the old one, so probably the new files will be uncompressed.
Am i wrong? 
If i'm not, who uses the compactor...need to re-compact the app every time there's an update...
do you think it's possible to automatize all this in some way?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Every officially released app has been run through the AppCompactor, as do (probably) the majority of beta test apps.
The AppCompactor isn't meant to be used on PortableApps by end users, but can be used on other apps. For PortableApps packages if the appcompactor.ini file makes it into the final install of an app you are essentially doing nothing, if the appcompactor.ini does not make it into the final install you are potentially going to break apps by compacting files that are not meant to be compacted.
In fact, a good chunk of them haven't been compressed.
Most (if not all) of the freeware apps aren't compressed, because that constitutes "modifying" the apps (and I don't think we've had permission to do that).
Firefox portable also isn't compressed either do to the licensing agreement.
And various other apps aren't compressed due to compatibility issues after compression.
And I'd say only about 52% of my apps are compressed with the compacter, mostly because of issues or because I've begun to lose my trust in believing the app compactor will keep the apps running 100% as well as it was before it was compressed.
I realize that some apps aren't compressed due to not working etc. after compression (and I also have two in beta that are uncompressed due to larger size after compression) but I thought I had read somewhere in the spec and/or related documentation that apps had to be compressed (or at least tried to have been compressed) to be officially released.
Maybe I just misread something...
the specifications discuss the AppCompactor, but don't specifically say it's gotta be attempted on all apps.
Think I found the bit I misread.
If you check the AppCompactor release page, under helpful hints there is a point "Only NRV2E should be used for PortableApps.com Releases...". I think I misread that point as saying NRV2E MUST be used for PortableApps.com releases.
Anyways, back to the topic at hand (and please ignore my previous comments as they have since been proven wrong), any app update that has been run through the AppCompactor prior to release will not see any improvement from having AppCompactor run on it again, and as long as each update has been compacted you don't need to worry about it.
But for apps that have not been compacted every update will overwrite your compacted files with uncompacted versions. Also as a further warning to what I said above if you use the AppCompactor on previously uncompacted apps there will be no appcompactor.ini file there, and thus you run the risk of breaking the app. So make sure you backup any apps before you try to compact them.
Having an app stop working can be fixed by simply reinstalling, but losing settings and/or data by compacting files that shouldn't be can't be undone if you don't have a backup of the file.
Really? :S
I noticed that trying to compress some apps is useless, cause the compression's already been made (as you said).
But with some other (see screenshot below) the compression is good, and the app is fully functional (or this seems to me, i didn't test still all the particular filters/editing).
http://i.imgur.com/SPkBh.png
As with anything there is the possibility of human error and someone having forgotten to compact it before posting. The only one who could really say for sure is the developer of the app.