fb2k-component packages vs zip files
Reply #11 – 2012-05-23 09:31:49
If you can install components manually without shooting yourself in the foot and also prefer updating them manually, that is good for you. Releasing the new ASIO component recently revealed that lots of people try to install components manually and end with corrupted installations by misplacing additional files bundled with the component that are required by the component to function. Hence the .fb2k-component format (yes, they are renamed zip files ), which encourages people to let fb2k handle the whole archive for them. Please do not recommend other users to install components manually; while the concept is still functional, it has been proven to cause problems - especially for "geek" users who think they know better how specific component should be installed.Yes but that only because foobar blocks updating components from this folder by design. It does not block updating components, it leaves them alone because it has no idea which additional files belong to which component....or "TAK Decoder" would get into an infinite updating loop Never heard of such issue. Have you posted about it in the tech support forum?or even if it did work properly, it left mess behind which I had to manually clean up by deleting files. Mess? Cleaning up? Downloaded files are left in a local cache folder to prevent server hammering if some component developer uploads a malformed package (which you seem to have witnessed with TAK Decoder). Sounds like you're too impatient to let foobar2000 automatically delete old downloads after one week.