On Thu, Aug 25, 2011 at 8:05 PM, Jian-feng Ding <[email protected]> wrote: > I think you need not to doubt the "-f" syntax of spec. It works well for a > quite long time. > What's the content in the dynamic generated *.files file? Maybe the errors > are from them.
Jian-Feng: Thank you for the reply and confirmation that "-f" works. My file was just a list of files to be included, much like I did in the first pass when I inserted the output of "find -f" into the spec file directly. Rather than having to update the spec file each time I add a QML file in development, I wanted to run 'find' in an earlier spec-file stage to get a list of all the QML files. Do you have a pointer to a working MeeGo 1.2 spec file that uses the "%files -f" syntax, and creates the files-list from in an earlier stage of execution in the spec-file? Also an example file in case there's some special tricky syntax, or documentation on that syntax? ( http://www.rpm.org/max-rpm-snapshot/s1-rpm-build-creating-spec-file.html didn't help, though looking again, I should run the examples from "rpmbuild -bl — Check %files list" from http://www.rpm.org/max-rpm-snapshot/ch-rpm-b-command.html ) If "-f" is working, in the following code: > elsif ($1 eq 'files') { readfiles ($files{$2} = [ ]); } > elsif ($1 eq 'pre') { readlines ($pre{$2} = [ ]); } > elsif ($1 eq 'post') { readlines ($post{$2} = [ ]); } > elsif ($1 eq 'preun') { readlines ($preun{$2} = [ ]); } > elsif ($1 eq 'postun') { readlines ($postun{$2} = [ ]); } > elsif ($1 eq 'files') { readfiles ($files{$2} = [ ]); perhaps the error message I'm getting is a bad way for the program to tell me it couldn't find the file? Next time I'm hacking spec files, I'll have to check the output of "rpmbuild -bl -vv meego.spec" to see if there's something else going on. In summary, perhaps the right question to ask is where should I be writing the file so that files -f can access it? ? In the previous failure output I posted, based on the file not being located as hypothesis for failure, I attempted a number of locations: > '%files -f /tmp/%name-qml.files' > '%files -f %{buildroot}/qmltube-qml.files' I also tried writing ../%name/qtc_packaging/qml.files in the master source tree, and referencing that filename as -f parameter. The builds are happening in a "shadow-build" environment run out of qtcreator 2.3RC0, so "../%name/qtc_packaging/qml.files" references the master source location relative to the shadow-build directory. Thanks. Niels http://nielsmayer.com _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
