On Thu, 2010-07-08 at 17:51 -0700, Ulrich Drepper wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 07/08/2010 09:05 AM, Chen Lei wrote: > > > It seems MeeGo builds core packages by using PGO already. Is there > > anyone who would like to volunteer to write a packaging guideline > > about using PGO? > > That's not so easy to generalize. As Jakub wrote, you need some form of > workload. After the binaries are built this workload has to be > executed. How to do that cannot really be summarized. Some packages > might need to be installed to function. Others need permissions etc. > Some might need interaction. For console programs you can do that using > expect but for GUI programs... > > After the workload is run you need to rebuild everything again while > pointing to the files created by running the workload. The first stage > binaries automatically create those files. > > Perhaps the best that can done is providing an example but I guess every > package needs to have its own way implemented. Is there a way to include pre-packaged workloads analysis? I realise we'd have to regenerate these somehow possible for each compiler update (not sure how the files look). This would allow us for some thing like firefox or openoffice to run some stuff offline on a packagers desktop and then use those files in a koji run later. Dave. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
