On 21 Mar 2003, seth vidal wrote: > On Fri, 2003-03-21 at 11:23, R P Herrold wrote: > > On Fri, 21 Mar 2003, Axel Thimm wrote: > > > > > Anyway, when I installed yum, I didn't imagine it would automatically update > > > the system over night. Wouldn't it we safer to have a "check-update" operation > > > instead of an "update", and leave it to the user to change it? > > > > This crossed the freshrpms list ... I had discussed this with > > seth a few evenings ago as well. > > > > I suggested that a more 'correct' default install should have > > the following attributes: > > -- disable kernel* and perhaps glibc-* by default > > Not sure that qualifies as "least surprise" Oh, please no. I agree this does _not_ qualify as least suprise. > > > -- install with the cronned yum process off, requiring the > > administrator to chkconfig it on in a given runlevel > > I agree here. One question, what happens during an upgrade? If I already have the yum service enabled does an upgrade kill it?? If so please keep the current behaviour. I can live with just about any default config as long as it does not constantly change and as long as _my_ config survives an upgrade. Since I control the repository I would prefer current behaviour but if a majority prefer it off so be it. > > > -- pull, but not apply automatically non-signed packages or > > packages without a known signature already on file. > > You can fill up disks with this - a notification seems reasonable as > something to do, though. I like the notification idea. -- .............Tom "Nothing would please me more than being able to tdiehl@xxxxxxxxxxxx hire ten programmers and deluge the hobby market with good software." -- Bill Gates 1976 We are still waiting ....
