An update manager similar to Tikal (http://tikal.sourceforge.net/index.html) made portable, that points to an online portableapps repository and verifies all the portable apps (exe's and zips) are up to date. Then I can choose whether or not to upgrade.
New: fb2kPortable / foobar2000 (Apr 18, 2024), Platform 29.4 (Apr 10, 2024)
1,000+ portable packages, 1.1 billion downloads
Please donate today
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
I guess noone understands what I am asking or not bothering to respond because it isn't possible.
I did attempt this, but I didn't get much interest.
----
R McCue
PortaBlog Home and My Website
And before anyone complains about the grammar, I'm so jetlagged that my
hands aren't even in the same time zone...
"If you're not part of the solution, you're part of the precipitate."
Maybe at the time it didn't make much sense because there weren't as many apps. Now as the list grows and the frequency of updates it may make more sense. I have a separate directory of all the apps from this site. If an update manager was used to compare the local directory from what is online then I would know of any updates and can choose to download. A lot easier than searching through the list, especially if you don't check out the website in a while.
And it was mentioned here, too. I think it is a little more complicated that it at first seems.
Don't get me wrong, I think it is a valid idea. I just don't think it will happen any time soon, at least until maintaining the apps becomes a lot easier task.
~Lurk~
~Lurk~
I'm working on an eventual solution to this. The problem is that we can't do automatic updates (something that downloads stuff directly) from SourceForge due to the fact that it uses a mirroring network. And I can't afford to host them on the server here (bandwidth for downloads would be $17,000 a month and rising). I'm working with RackSpace on cutting a deal regarding bandwidth for later this year, though.
My plan is multi-fold (it's a word now):
1. Include an INI or XML file within each app that includes version info and an update URL (that was the AppInfo directory I was including but am holding off on until I finalize a few things)
2. Place files at the update URLs that indicate current version
3. When there's an update, download the appropriate file (it'll be in 7z format to save on bandwidth and install speed) and apply it
As Lurk guessed, one of the reasons I've updated all the apps to do in-place upgrades is to prep for a future updater along these lines. It won't be in time for the 1.0 release of the suite and menu. But it will be in the next couple months. I'll be posing it to the community here for opinions on structure and formats, so we can arrive at something solid that will work for any portable app (whether or not it's hosted here).
Sometimes, the impossible can become possible, if you're awesome!
Check out my one I tried. Might save you some coding.
----
R McCue
PortaBlog Home and My Website
And before anyone complains about the grammar, I'm so jetlagged that my
hands aren't even in the same time zone...
"If you're not part of the solution, you're part of the precipitate."
Don't get me wrong, I think it is a valid idea. I just don't think it will happen any time soon, at least until maintaining the apps becomes a lot easier task.
Seems like that time is a lot closer than I thought!
~Lurk~
~Lurk~
Hello John;
I know you are busy. This post is not meant to ask for a update. This is just a question about how often or if you have given any thought to how often the entire suite would be updated.
I like the complete single down load. I all so can just down load newly released portable apps and replace the older ones. This is what I have been doing. But I just had to ask if you have come up with any idea on this. I all so know that some of the apps do get updated often.
Frank D. Hubeny