HaikuDepot doesn't autorefresh repos on first Launch.

[kallisti5]

When launching HaikuDepot on a freshly installed Haiku system, the "All Packages" tab doesn't contain a complete inventory of software @ Haikuports, and could give a first impression of "Haiku doesn't have any software"

I think the repos are pre-populated with the software available in the Jam build repos? After manually doing a refresh, the full set of packages on the "All packages" tab are visible.

HaikuDepot should attempt an autorefesh on first launch? Open to ideas.

hrev52775

[vidrep]

hrev53152 x86_64

This is still a problem on fresh installs. Only 4 packages show up in the "featured Packages" tab on first boot. After refreshing the repositories, then the list is fully populated.

[diver]

According to videos on youtube and Telegram this gives a really bad first impression on Haiku itself. With haiku-master-hrev54185-x86_64-anyboot.iso only 3 packages show up in HD.

[diver]

Tried again with haiku-master-hrev54249-x86_64-anyboot.iso.

Booted to the Desktop without installing.

It appears that the problem is that /system/cache/package-repositories/HaikuPorts is only ~70KiB. After refreshing the repos it jumps to 1.24MiB and displays all the packages.

I wonder why HaikuPorts cache is so small in the iso?

[waddlesplash]

Because these are the build-packages repository files, which contain only the packages required to build Haiku itself.

[diver]

Though so. Should HaikuDepot force the update if HaikuPorts cache file is less than 1mb? Or something more sophisticated is better?

[waddlesplash]

It should just plain force it on first startup (i.e. if there is no HaikuDepot cache, also refresh repos.)

[apl-haiku]

I have had a look through this. The logic is actually there to refresh from the remote repo, but it is only happening when there is no cache present. When Haiku is installed it has a cache present from the build process so HaikuDepot does not download the repo data. As it happens, easy to fix, but there are a few options as to how to best approach this.

• Create a background task / script to run independently of HaikuDepot when Haiku first starts in order to update the repositories' data and don't make a change in HaikuDepot's logic at all.
• Update the repositories' data on every start of HaikuDepot and every time that the user chooses "Refresh repositories"
• Update the repositories' data only the first time that HaikuDepot runs and every time that the user chooses "Refresh repositories"
• Update the repositories' data at most once a week as well as when HaikuDepot first runs as well as every time that the user chooses "Refresh repositories"

Downloading the data each run of HaikuDepot is not always quick and adds to the overhead at start time. Any thoughts from the audience?

[waddlesplash]

Options 3 and 4 sound the best; if the cache files are over a week old, run the upgrade; or if this is the first time HaikuDepot is starting, run the upgrade.

[waddlesplash]

Change merged in hrev54276. Diver, please test :)

[diver]

While there is no fresh beta2 image yet I guess I can test using a regular nightly.

[diver]

Compiled HaikuDepot from master and tested it on pre-beta2 install and it's working. Thanks!