Dear Toan, On 20.11.2009, at 16:51, Toan Pham wrote:
> > Rene, > > I looked in the SDE and I could not find how you generate flist file > for each installed package, ie. > all files under $build_root/var/adm/flist/<package name> > I did not know what mechanism you use to determine all installed files > for each package. > Also, I tried entering the sandbox and manually install some files, > ie. install README / > and that did not include the file /README to a package file list. > Would you please tell me how it is done, and also if it is possible to > custom install some more > files during a package build procedure and have these files included > in the file $build_root/var/adm/flist/<pkgname> the build installed files are tracked by the selected "trace" technique, which is a LD preload library by default. Historically we also provide a strace choice (but I did not test it in a long time and it is slow anyway). If you install other files in the package they should appear automatically in the flist, by said "tracer". Unless you install the files in the postinstall hook, which is post the point where the build is "traced", for this the add_flist helper can be used (with care) to add the file. -- René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin http://exactcode.com | http://t2-project.org | http://rene.rebe.name
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
