Assumed this question was coming. I had given this a lot of thought. I have this crazy notion that nothing should ever be installed and bootstrapping is really annoying. I felt it was easier to just launch an AMI.....yet again, why not just repackage another image.
The automated build nature of what I do requires me to repackage some lower level libraries so they can link easily and stably (is that a word?) across multiple packages. I also have some longer term objectives that will require me to have complete control over the kernel and packaging. It just seemed easier to start my own thing for this. Agree, this could prove insane. If that is the case, it wouldn't be *too* hard for me to convert this to some package repo On Thu, May 3, 2012 at 9:53 AM, Darren Govoni <[email protected]> wrote: > A distro would be good and if it was made into an Amazon Machine Image so > we can spin it up and use it _without_ having to install it, that's a good > thing too. > > So the best approach is always both! > > <br><br><br>------- Original Message ------- > On 5/3/2012 11:42 AM Dan Brickley wrote:<br>On 3 May 2012 18:34, Ted > Dunning <[email protected]> wrote: > <br>> Thanks for including Mahout. > <br>> > <br>> As a point of strategy, wouldn't have better to just build a debian > package > <br>> repository and a script for installing packages? That would allow > people > <br>> to use their own debian or ubuntu based distros for their own > special needs > <br>> such as hardware virtualization or special kernel modules and still > get the > <br>> benefits that you are offering. > <br>> > <br>> Otherwise, you are sentencing yourself to a life of hard labor > keeping up > <br>> with kernel updates and such. > <br> > <br>I was about to ask the same question... why a whole distro? Unless the > <br>whole thing is a highly-tuned and unusual setup, some install scripts > <br>are often good enough. > <br> > <br>Dan > <br> > <br> >
