Gerard Henry wrote:
> Damien Carbery wrote:
>
>>> in logs, i got these errors:
>>> pkgbuild: Install README.txt
>>> /var/tmp/pkgbuild-devel1/SFEtix-8.4.3-build/usr/lib/Tix8.4.3/README.txt
>>> pkgbuild: + exit 0
>>> pkgbuild: pkgbuild: File not found by glob:
>>> /var/tmp/pkgbuild-devel1/SFEtix-8.4.3-build/usr/bin/*
>>> pkgbuild: pkgbuild: File not found by glob:
>>> /var/tmp/pkgbuild-devel1/SFEtix-8.4.3-build/usr/share
>>> pkgbuild: pkgbuild: File not found by glob:
>>> /var/tmp/pkgbuild-devel1/SFEtix-8.4.3-build/usr/share/man
>>> pkgbuild: pkgbuild: File not found by glob:
>>> /var/tmp/pkgbuild-devel1/SFEtix-8.4.3-build/usr/share/man/*
>>> pkgbuild: pkgbuild: File not found by glob:
>>> /var/tmp/pkgbuild-devel1/SFEtix-8.4.3-build/usr/share/man/*/*
>>>
>>>
>> In the %files section of your spec file you have lines like:
>> %{_bindir}/*
>> %{_datadir}
>> %{_mandir}
>> %{_mandir}/*
>> %{_mandir}/*/*
>>
>> They tell the build tools to include files that are installed to those
>> locations (they are installed to a temp area called $RPM_BUILD_ROOT,
>> generally under /var/tmp/pkgbuild-username).
>>
>> Remove those lines and rebuild. Repeat until you stop getting those errors.
>>
>> You may get errors about unpackaged files e.g.
>> pkgbuild: error: Installed (but unpackaged) file(s) found:
>> pkgbuild: /usr/lib/python2.4/vendor-packages/gstoption.so
>> pkgbuild: /usr/lib/python2.4/vendor-packages/gstoption.la
>>
>> This is where files are copied to $RPM_BUILD_ROOT but not listed in %files
>> In the above example I added the following line to %files:
>> %{_libdir}/python2.4/vendor-packages/*
>> (My actual line was slightly different but I'm keeping the answer here
>> simple)
>>
>>
>
> it seems that my problem is different, because when i look into
>
> /var/tmp/pkgbuild-devel1/SFEtix-8.4.3-build/usr/, there is no share
> directory, and bin is empty. In fact, playing with "make -n install" to see
> what files will be installed, i notice that Tix will install everything in
> /usr/lib/Tix8.4.3 and there are no man, and no share dirs. I have to
> understand how to write the %files section.
>
ok, reading docs is better :) i now understand (but a little) what i
need to put in %files (after many tries-errors):
%files
%defattr(-, root, bin)
%doc README ChangeLog CREDITS COPYING INSTALL NEWS AUTHORS TODO ABOUT-NLS
%dir %attr (0755, root, bin) %{_bindir}
%dir %attr (0755, root, bin) %{_libdir}
%{_libdir}/*
this is correct for me, even if i don't understand why i need to specify
%_bindir because this directory is left empty by Tix
and if a guy (me for example) do a mistake in %attr, many problems again...
Another question if possible:
if you want to change the args of configure script (for example to take
a new lib into account or to change cc to gcc?) you have to write a
different spec file for each differents args?
--
Gerard HENRY
