<html>
<head>
<style type="text/css">
<!--
body { margin-top: 4px; margin-left: 4px; line-height: normal; font-variant: normal; margin-bottom: 1px; margin-right: 4px }
p { margin-top: 0; margin-bottom: 0 }
-->
</style>
</head>
<body style="margin-top: 4px; margin-left: 4px; margin-bottom: 1px; margin-right: 4px">
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">All,</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">ok, I've been watching on the sidelines here, and also have a few minutes to chime in . . .</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">I'm going to suggest something a little bit of left field here too, may even go beyond the OSGEO borders as well.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">Has anyone thought about a online package builder, something that handles the dependencies automatically, but allows for different packages to be chosen by the user. The best comparison I can think of right now, would be something like CPAN for PERL, but for assembling OSGEO stacks (plus others?)</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">This is something I've been pondering from the USB build side for example, and the two different approaches might be combinable some how. Also, it allows for a slower more measured build-out as each package can be added incrementally as time goes on, assuming a registration method could be had to facilitate inclusion. By also using a build mechanism like this, multiple starter packages can exist as well as possible even registering custom packages later on for others to reuse.</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">Just spit balling here, but it seems like saying something earlier rather than later . . . .</font> </p>
<br>
<p style="margin-bottom: 0; margin-top: 0">
<font face="Comic Sans MS" size="3">bobb</font> </p>
<br> <br>
<p style="margin-bottom: 0; margin-top: 0">
<br>
<br>
>>> Cameron Shorter <cameron.shorter@gmail.com> wrote:<br> </p>
<div style="border-left: solid 1px #050505; background-color: #f3f3f3; margin-top: 0; padding-left: 7px; margin-left: 15px; margin-bottom: 0; margin-right: 0">
<p style="margin-bottom: 0; margin-top: 0">
Tom,<br>Our FOSS4G conference is over, and our LiveGIS team are starting to plan<br>for our next release (probably in March 2010).<br><br>Some of our pain points in the last release were:<br>* Click2Try were only brought in at the last minute, and hence we had a<br>number of bugs in click2try which were being addressed under the<br>pressure of a tight deadline.<br><br>* Because we were so focused on the development, and the FOSS4G<br>conference, we only had limited time for marketing and engaging with the<br>user community.<br><br>* Many of our packagers have limited bandwidth, and consequently are not<br>in a position to download multiple iterations of a distribution themselves.<br><br>Consequently,<br>I wonder whether click2try would be interested in providing our team<br>with a few online development servers which we can use to build our image.<br><br>What are your thoughts here?<br><br><br>--<br>Cameron Shorter<br>Geospatial Systems Architect<br>Tel: +61 (0)2 8570 5050<br>Mob: +61 (0)419 142 254<br><br>Think Globally, Fix Locally<br>Geospatial Solutions enhanced with Open Standards and Open Source<br><a href="http://www.lisasoft.com">http://www.lisasoft.com</a><br><br>_______________________________________________<br>Live-demo mailing list<br>Live-demo@lists.osgeo.org<br><a href="http://lists.osgeo.org/mailman/listinfo/live">http://lists.osgeo.org/mailman/listinfo/live</a>-demo<br>
</p>
</div>
</body>
</html>