FYI... I did some quick testing with 2.3.4 and RPMCALLBACK_REPACKAGE_PROGRESS still isn't set multiple times during the repackaging processing as would be expected (although it is set once for every package that is repackaged.) RPMCALLBACK_INST_PROGRESS is set instead. Thanks (Seth) for adding progress bars and other general output during the repackaging process. ~Chris On 7/20/05, seth vidal <skvidal@xxxxxxxxxxxx> wrote: > > > > > > So I'm looking at this patch and I'm trying to figure out what > > it > > actually _does_. > > > > It seems like you just added 'pass' for all the > > RPMCALLBACK_REPACKAGE_* > > cases in the rpm callback. Shouldn't we be outputting > > _something_ so the > > user knows the repackaging is going on? If only b/c > > repackaging could > > take a while and it looks a bit odd that nothing is being > > outputted > > during this time. > > > > What do you think? > > > > -sv > > > > Sorry for the long delay in getting back. > > > > I totally agree that process status needs to be shown, but I didn't > > even attempt it because I still don't get why the callbacks are called > > as they are when repackaging. From my original email... > > > I fixed up the callbacks before I checked them in - check out yum 2.3.4 > see if that works for you. > > -sv > > > > -- Christopher C. Weis |---> Enterprise Systems Manager/Administrator |---> ccweis@xxxxxxxxx |---> http://www.weiserthanbefore.com (blog and gallery) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.dulug.duke.edu/pipermail/yum/attachments/20050730/4b7ee9f3/attachment.htm
