| 1 |
On 08/17/2010 01:23 PM, Elmar Hinz wrote: |
| 2 |
> Hello folk, |
| 3 |
> |
| 4 |
> I am currently working on a tool, a USB-stick, |
| 5 |
> to set up a typical freelancers development environment the easy way. |
| 6 |
|
| 7 |
This sounds like pure image distribution without installing anything, |
| 8 |
at least not "installing" the binary packages in portage-speaking. |
| 9 |
|
| 10 |
To get this working on the target machines, your USB-stick content need to be |
| 11 |
available at the very same location as where it was built for, even on Windows. |
| 12 |
As long as you don't need a C/C++-Compiler, symlinks should do on Linux & Mac, |
| 13 |
because there is a (still unconfirmed) bug in gcc breaking with symlinks, which |
| 14 |
should be fixable though. IIRC, there is some mechanism to mount something |
| 15 |
to some location more complex than just a drive letter on windows. |
| 16 |
|
| 17 |
> 1.) I want to run it on any computer, --> Win, Lin, Mac. |
| 18 |
> |
| 19 |
> So it has to be platform independent. |
| 20 |
|
| 21 |
Well, the source of your tool can be platform independent, |
| 22 |
but your USB-stick content does not. You will have to create |
| 23 |
either different USB-sticks, or different paths on one stick |
| 24 |
for each target platform. |
| 25 |
|
| 26 |
> 2.) I want install it up and running. |
| 27 |
> |
| 28 |
> the usual OSS stuff: SVN, Eclipse, Apache, Java, etc. |
| 29 |
|
| 30 |
This sounds like pure Java development: |
| 31 |
When you do not need a C/C++-Compiler in your target image, nor any |
| 32 |
unixish shell scripts or unixish path operations, in theory it *might* |
| 33 |
be possible to provide the windows image without any Interix part, so |
| 34 |
you need Interix on your build machine only. |
| 35 |
But this would be really hard work. |
| 36 |
|
| 37 |
> The auto configuration is the task of my tool. |
| 38 |
> |
| 39 |
> |
| 40 |
> 3.) Best to do it without root permissions |
| 41 |
> |
| 42 |
> in example in $HOME/workspace/ |
| 43 |
|
| 44 |
I doubt you can "provide" your images within this path. But it should |
| 45 |
be possible to have your Eclipse(?) "use" this path at Eclipse's runtime. |
| 46 |
|
| 47 |
> OK, guess starting Apache requires root privileges. |
| 48 |
|
| 49 |
Although I don't really know about Apache, it should be possible for any |
| 50 |
user to run it on any unprivileged port (>1024). |
| 51 |
|
| 52 |
> 4.) A want to versionize also the environment sources (servers) |
| 53 |
> |
| 54 |
> I want be able to restore any development version |
| 55 |
> of a project in it's original runtime environment. |
| 56 |
|
| 57 |
Unclear what you mean with "project" as well as "runtime environment". |
| 58 |
|
| 59 |
> Is is stable enough? |
| 60 |
|
| 61 |
I'd say it depends on your qa- and distribution-requirements: |
| 62 |
|
| 63 |
If you do your image releases once in a while without upgrades, |
| 64 |
you might want to do this based on the original prefix tree, and |
| 65 |
get it working again before your next release. |
| 66 |
|
| 67 |
If you continuously have to be able to provide *tested* images or upgrades, |
| 68 |
or to distribute from source, I'd prefer maintaining stable keywords in a |
| 69 |
fork of tree once it works, cherry-picking changes back and forth, so you |
| 70 |
have total control over your tree and its stability - even if you get out |
| 71 |
of date quite quickly. Because I doubt the prefix project gets enough |
| 72 |
manpower to maintain stable keywords soon enough. |
| 73 |
|
| 74 |
HTH, |
| 75 |
/haubi/ |
| 76 |
-- |
| 77 |
Michael Haubenwallner |
| 78 |
Gentoo on a different level |
Archives