Not use PBI in 2.1 (yet!)
-
We have some custom packages (tbz) and we want to continue to use them in 2.1 release until they not be ported to PBI format, is it possible?
My question applies to the the automated process of installation (via WebConfigurator).We have our own repository…
Thanks!
-
It is.
-
Can you share with us, how it is possible?
-
Anyone?
-
Don't understand your question. Non-PBI packages that were working with 2.0.3 are working the same way with 2.1. PBI is just a new type of packaging, old style still works as before.
-
Sorry… Let me explain better...
My question is: How can I put in my local repository a package that works in both releases (2.0.3 and 2.1), but, I want to force the installation behavior in 2.1 be the same as 2.0.3 (using TBZ instead PBI).
That's possible?
-
In the time you've spent tracking this down, you could have built a PBI already. It's not terribly difficult, I've described the process before here on the forum.
-
Thanks Jimp!
I'll search for this Topic… but I've noted that the size of the PBI packages is much greater than the TBZ ones... In case of embedded platforms that is a problem... -
It can be much larger but it's also much safer since the programs are isolated and can't stomp on each others' libraries.
-
In the time you've spent tracking this down, you could have built a PBI already. It's not terribly difficult, I've described the process before here on the forum.
Could you please give me the link of that post? I was unsuccessful using the search engine…
-
If you search for rebuild_package_binaries_pbi.php you'll find a few relevant topics. (Use google, not the forum search)
