Although Haiku has a good package management, and knowing the [common insert untrusted binary download warning here] that we know about, would be interesting to have some kind of bundled app that include the required dependencies for big apps?
Something like AppImage on Linux (or FlatPak/Snappy, but those require a server, i mean ones for standalone apps), or just port the AppImage tools to make Haiku AppImages.
Well, why not just copy packages? That’s usually what I do and it’s easy enough, provided the systems are the same hrev. Packages usually have what they depend on, so it’s usually just a matter of rounding up what you need into a folder or what not and copying it.
Personally, I’m usually very open minded about new ideas, but after all the work put into the PackageFS, it’d be a shame to slow down Haiku development to pursue app images. Just my little opinion. And maybe others might think AppImage or the like is a wonderful idea. So, anyways, that’s just me…
A lot of Windows applications are still distributed as a zip file with the executable as well as every dll file that the application depends on. You can extract it anywhere you want and it’s ready to be used. I would very much like to see more of this in Haiku.
That may not be a good idea in long-term use since what happens with most users is that they will be scattered almost everywhere throughout the file system. Many will be in the Downloads/User/Home folder, others on the desktop, in a different drive, some seemingly random location, et cetera. Perhaps something like AppImage (if not that per se) would be the better approach, where all the files are stored in a container format (not containers) that can just be brought around and executed instead of extracting the contents and creating a mess.
Because you cant have (that i know of) a GTK2 application that uses cairo 1.13.x (providing pkg-config library ‘cairo’) and this new app GTK3 that rocks but requires cairo 1.14.12 (same ‘cairo’ pkg-config name). You can, so statement is not a good example.
Also, because there might not be a recipe yet for a dependency.
If the packages are available, then yes, packages all the way, just pkgman-em.
You can distribute your hpkg and the package manager will automatically download dependencies when users install it. So it works just as an AppImage: double click to install, then run. Escept it also allows us to distribute security updates without relying on the application developers to do so.
Just put the needed files in a .zip and call it a day then. No need for something fancier. By default the OS will find libs in a “lib” folder next to the executable so you can just put your libs there.
There isn’t much point in doing that nowadays I think, but it’s the way BeOS apps worked and it’s of course still supported. There is no need for a custom bundle thing when a plain zipfile does everything we need, right?