On Mon, 2005-06-06 at 18:00 +0200, Matthias Bethke wrote:
the only remaining problem I
can think of right now (I'm sure others will pop up once I try it ;)) is
configfile management. A nightly removal of all the ._cfg* files plus
some scheme to keep the configs in sync with an SVN server
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ow Mun Heng wrote:
Yep. That is most certainly a problem. Unless of course you're so sure
and you can remove CONFIG_PROTECT and then get use buildpkg's to package
in the created tbz2 with the new updated configs. (yeah, you can't use
--buildpkg
On Tue, 2005-06-07 at 12:47 +0530, Aniruddha Shankar wrote:
Ow Mun Heng wrote:
Yep. That is most certainly a problem. Unless of course you're so sure
and you can remove CONFIG_PROTECT and then get use buildpkg's to package
in the created tbz2 with the new updated configs. (yeah, you can't
On Mon, 06 Jun 2005 09:14:07 +0930, Iain Buchanan wrote:
why? Isn't this essentially `emerge --buildpkg` ?
Have you looked at buildpkg Matthias? I've used it before on similar
machines. Seems to work ok. Granted, you can't just `emerge -upD
world` on the copies, but you may get away
Hi Neil,
on Monday, 2005-06-06 at 09:08:53, you wrote:
Have you looked at buildpkg Matthias? I've used it before on similar
machines. Seems to work ok. Granted, you can't just `emerge -upD
world` on the copies, but you may get away with minimal effort.
You can if you use a shared
On Fri, 2005-06-03 at 20:55 -0400, Antonino Sabetta wrote:
Matthias Bethke wrote:
If there were such a script that could copy the binaries and the new
files to all the other machines I would probably not trust it! :)
why? Isn't this essentially `emerge --buildpkg` ?
Have you looked at
There's some SuSE-based workstations around me here I have to take care
of. I guess they won't have to bear SuSE for much longer though.
The alternatives I can imagine now are Debian and Gentoo. Personally I'd
prefer Gentoo, but I don't feel like reinventing the weel by writing my
own deployment
mentioning such setups here, so I guess somebody has developed the stuff
I'd need already? I'd be thankful for any hint or pointer...
This does not answer you question, but probably could be a partial
solution: have you considered cloning the hd of the 'first' machine
and then copying it to the
Hi Antonino,
on Friday, 2005-06-03 at 20:55:43, you wrote:
So you're actually trying to reuse even the compilation work performed on
the 'first' (let's call it 'master') machine and avoid compiling on all
the others when you do an emerge --update world for instance?
That was my idea, or rather
9 matches
Mail list logo
