On Mon, Jun 20, 2005 at 02:53:06PM +0200, Holger Levsen wrote: > On Monday 20 June 2005 14:29, you wrote: > > > Why ? If you do softupdates, your machine has been set up allready. > > ?! > > prepareapt copies the dpkg and apt conffiles _before_ messing around with > > apt; if an updated sources.list points to sarge while it pointed before at > > woody, you are able to pull your box from woody to sarge without > > reinstallation. > > Even though this is nice and fancy, it's a bad hack. IMHO you should > provide/use classes WOODY and SARGE and use scripts/SARGE to change
that's exactly what I'm doing. > sources.list on that machine. In task_configure not in task_prepareapt. not really: all software updates/installation takes place _before_ task_configure; re-calling apt-get dist-update and install_packages in task_configure would be a bad hack. task_prepareapt is the place where all package manager configuration should take place; just imagine you add/remove repositories from the sources.list for different classes. > I'm aware that your approach is slightly more effective/faster, but I do > believe it's to hackish. > > On softupdates apt is set up allready. No need (and no sane way) of updating > it _as_default_. 'correctly' in terms of the state of the last install/softupdate. in terms of the current run it is not. > > > please not as DEFAULT. Maybe in FAIBASE which I propose not to use in > > > default softupdates ;-) > > that's what _I_ use in the config for my machines here, which is quite > > different from the fai simple-example. > > Please keep in mind the scope of the simple examples... (which in a lot of > peoples opinion should become part of a default config some day.) this hook is not intended to be merged into the simple examples; it is simply what _I_ am using to circumvent the missing fcopy in task_prepareapt. -- c u henning -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
