On Sat, Jan 30, 2010 at 03:59:27AM -0800, Zac Medico wrote: > On 01/28/2010 09:24 PM, Max Arnold wrote: > > On Thu, Jan 28, 2010 at 04:17:41PM +0100, Beber wrote: > >> So, do you guys plan to implement a such thing ? That's one of the > >> features that is mostly missing imho. The principal miss in on client > >> side as I have tools to manage packages but would like to not have too > >> much specific scripts on client side. > > > > I like the way it done in OpenEmbedded. You have the tree of recipes (think > > of portage tree) > > and bunch of targets. For each target BitBake can generate binary release > > and package feed. > > Client package management is lightweight and does not require BitBake, > > recipes tree and even > > python. At least this is my lame interpretation of how it works :) > > You can do something similar using the emerge --config-root option. > You'd just use a different --config-root for each target, and each > of those would have a separate $PKGDIR.
Can someone share his experience of using Catalyst or Metro as generator of binary package updates for precompiled client machines? How smooth it is in the long run?
