On Thu, 2004-01-15 at 16:08, Karsten Jeppesen wrote: > Thanks, > > > I think you might be looking for pkgpolicy=last in your yum.conf. > > No - I will make certain that my package is newer - at least the > version will. But it certainly fixes the problem. > Which raises the question: newest? release/version or upload date??? > The problem is as follows: > > When Yellowdog releases a kernel update they should release one for the > briQ as well. Currenty 2.4.20-8e. > But I am at 2.4.23 soon 2.4.24. > But after I post the 2.4.23 on my YUM repository I want the briQs out > there to say: > 1) .... base is YDL: 2.4.20 (oct 2003) > 2) .... update is YDL:2.4.20-8e (jan 2004) > 3) .... Total Impact is 2.4.23 (dec 2003) > hmmmmmm - 3 is the better one - I will update to that one. (last does > fix it!) > > If YDL released 2.4.24 tomorrow, then I would release 2.4.24-99 right > away to counter it for the briQs. date has nothing to do with the version comparison. -sv
