On Sat, Nov 12, 2011 at 16:17, Richard Purdie <[email protected]> wrote: > On Sat, 2011-11-12 at 13:57 -0200, Otavio Salvador wrote: >> On Sat, Nov 12, 2011 at 06:36, Richard Purdie >> <[email protected]> wrote: >> > Currently bad recommendations are added to the status file with status >> > "ok". After a single opkg command, whilst it will ignore the >> > recommendation, >> > the status changes to "installed" even if the recommended package was not >> > installed. Whilst this is likely a glitch in opkg's logic, the correct >> > way to persist the information in the status file is to set the status >> > to "hold" as deinstall packages with that status remain. With this change >> > the bad recommendations persist accross multiple opkg runs and the system >> > behaves as expected. >> >> I personally dislike fixing it in rootfs_ipk instead of opkg ... opkg >> has change its behaviour behind the scenes and this needs to be fixed >> IMO. > > I'm not sure opkg has changed behaviour. We used to just do one single > "opkg install" after which the status file was incorrect but the bad > recommends was not installed. We started doing more than one "opkg > install" and this has muddied the waters so to speak. I'm still unclear > if the bad recommends actually make it onto the target system but > certainly the status file was incorrect.
It does end onto the target. > The summary is we were not using opkg correctly in the first place. This > patch corrects that problem so we do what we what that code intended to > do and persists the bad recommend into the status file. This fixes the > bug that was reported too. > > There look to be remaining issues in opkg but not ones that directly > affect the build system. Please do take this up with the opkg people but > I'm afraid I personally don't have time to start debugging opkg and I > think there are other more urgent priorities at the moment now this is a > non-issue for the builds. This does fix the problem we were having but I am concerned about other possible behaviour changes it might happen. I think this patch ought to go but someone skilled on opkg might take a look at opkg code to see if this isn't a regression of lately changes. -- Otavio Salvador O.S. Systems E-mail: [email protected] http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
