Difference between revisions of "Deployment"

Line 79:

* Everything in one directory (this is what already exists) and this can be copied everywhere. This is the more simple but works only for Win

* Packages plus simple scripts for Linux. We could also think about packages downloading an installing content over a LAN base on P2P.

But for almost all of these approaches, the challenge is to build the "base package":

* What if do not have internet and need component which are not local?

* How to do that, HOWTO, GUI to make that?

* A lot of people want to make portable what they have on their computer. Is that the good way of doing?

== Current bugs & features requests ==

Navigation menu

@@ Line 79: / Line 79: @@
 * Everything in one directory (this is what already exists) and this can be copied everywhere. This is the more simple but works only for Win
 * Packages plus simple scripts for Linux. We could also think about packages downloading an installing content over a LAN base on P2P.
+But for almost all of these approaches, the challenge is to build the "base package":
+* What if do not have internet and need component which are not local?
+* How to do that, HOWTO, GUI to make that?
+* A lot of people want to make portable what they have on their computer. Is that the good way of doing?
 == Current bugs & features requests ==