[bitbake-devel] hashequiv, pseudo, and GIDs

chris.laplante at agilent.com chris.laplante at agilent.com
Wed Dec 11 15:01:47 UTC 2019


> > A workaround is to add:
> >     DEPENDS += "B"
> > to recipe A, so that the group ends up in A's pseudo database. This
> > works, but seems really really hacky, since it's only necessary when
> > hashequiv is active.
> 
> I suspect this isn't a hack, but necessary and you're finding a
> determinism/missing dependency issue that hashequiv is highlighting?
> 
> > So why is the group name used in the hash, as opposed to the GID? (I
> > also have the same question regarding user name vs UID). If the GID
> > was used we wouldn't have this issue.
> 
> The only way I can think this might work is that you're statically
> assigning GIDs and using the GID directly in do_install? That isn't the
> way the defaults are setup.
> 
> If that is the case we probably have to detect it and change the
> behaviour of hashequiv's comparison function to use UID/GID but it does
> depend on the wider system setup.


Yes, you and Josh are correct. The recipe was doing "chgrp 3004". It definitely makes sense for me to add the dep on B, and change it "chgrp actual-group-name". But like you said I think it does expose a problem in hashequiv.

Chris 


More information about the bitbake-devel mailing list