[Toaster] FW: question and possible bugs about Target_File

[Lerner, Dave]

> From: Reyna, David
> Sent: Wednesday, March 12, 2014 12:11 PM
> To: Lerner, Dave
> Subject: RE: question and possible bugs about Target_File
> 
> > 3) the build created entries orm_target_File entries for paths "/usr/bin/["
> > and "/usr/bin/[[" .
> >
> 
> Those are real files.
> 
> - David
> 
> > -----Original Message-----
> > From: toaster-bounces at yoctoproject.org [mailto:toaster-
> > bounces at yoctoproject.org] On Behalf Of Lerner, Dave
> > Sent: Wednesday, March 12, 2014 10:06 AM
> > To: DAMIAN, ALEXANDRU
> > Cc: toaster at yoctoproject.org
> > Subject: [Toaster] question and possible bugs about Target_File
> >
> > Hi Alex
> > I've noticed some possible anomalies in the adamian/fixes_06032014
> > construction of Target_File:
> >
> > 1) you have files of inode type 1 ITYPE_REGULAR but with sym_target non-empty
> > implying a symbolic link.  That makes some sense if you plan on exposing the
> > 'type' of the linked to file, so that for example, a directory inode linked
> > to another directory is of type directory, which makes my life easier since I
> > don't have to follow links to find if the underlying type is a directory,
> > which changes logic in the view.  For symlinks resolving to directories, the
> > non-empty sym_target implies the link type, and leaving inodetype=directory
> > helps.
> >
> > 2) none of the entries in /dev/ have inode type character or block. There are
> > only file and directory inodetypes 1 and 2 in orm_target_file after 3 builds
> > of minimal and sato.
> >
> > 3) the build created entries orm_target_File entries for paths "/usr/bin/["
> > and "/usr/bin/[[" .
> >
> > -dave
> > --
> > _______________________________________________
> > toaster mailing list
> > toaster at yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/toaster