I wonder if relocatable DEBs are possible. (Some quick googling suggests not?) If not, relocatable RPMs would be a substantial amount of work for a half measure.
I also think that if looking for deployment vehicles supporting concurrent installation of multiple component versions, we'd be better served putting project energy into LXC based deployment management and packaging. (That could be _really_ interesting, if for example containers have a late binding on dependencies, where they ask other containers during boot and service discovery to supply them with packages to install... I know, a crazy idea, not meant to lead this discussion off on a tangent) On Wed, Jul 9, 2014 at 2:45 PM, Sean Mackrory <[email protected]> wrote: > Like Peter, I believe this would be a substantial amount of work. > Relocatable RPMs work well when you mainly need a bunch of files installed > on the machine. However, Bigtop is a collection of interconnected > components and files that integrate them with the service and configuration > management of the host OS. That is not so easy to do in a relocatable > manner. > > > On Wed, Jul 9, 2014 at 2:45 PM, plinnell <[email protected]> wrote: > >> On Wed, 9 Jul 2014 12:30:10 -0700 >> Jing Wang <[email protected]> wrote: >> >> > I have been looking at BigTop and was trying to generate RPMs for a >> > few Hadoop related projects. However, the RPMs generated are not >> > relocatable. Just want to check if I am missing out on some >> > configuration parameters for generating relocatable RPMs or this is >> > not supported yet. >> > >> > Thanks, >> > >> > Jinghui Wang >> >> Hi, >> >> Just curious why you need them relocatable ? I suspect a lot of work >> would go into enabling this and a lot testing to make it work. >> >> Thanks, >> Peter >> > > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
