No edit summary |
|||
Line 42: | Line 42: | ||
== file-not-in-%lang == | == file-not-in-%lang == | ||
This is a real error. You can use <code>%find_lang</code> with MinGW packages, although the exact usage isn't that obvious. Use it like this: | |||
Name: mingw32-foo | |||
%install | |||
%find_lang foo | |||
%files -f foo.lang |
Revision as of 17:52, 22 January 2009
Common rpmlint warnings and errors
Some rpmlint warnings and errors are generated by MinGW packages. This page explains what they mean and whether they can be ignored. Also details of long-term plans to get them fixed.
In general we hope that some future version of rpmlint will be released that allows us to ignore certain warnings for MinGW packages.
devel-file-in-non-devel-package
All MinGW packages are for development only, so when we passed
the guidelines we didn't opt to have a separate -devel
subpackage,
since the main package would just be empty.
See bug 468987.
script-without-shebang [some .la file]
We use *.la
files when linking. This is explicitly allowed in the MinGW guidelines that were passed.
Longer term we would like to check whether *.la
files
are genuinely necessary, and whether we can remove them.
spurious-executable-perm
See this comment for a detailed explanation.
arch-independent-package-contains-binary-or-object
See bug 468989.
non-standard-dir-in-usr i686-pc-mingw32
This breaks the FHS, but is permitted by the MinGW guidelines.
These directories in /usr
are ugly, but are commonly
used by cross-compilation tools.
The FHS project upstream is dead, so we can't get the directory added
to the standard. It is thought to be very complex to remove the need
for this directory from gcc and binutils.
file-not-in-%lang
This is a real error. You can use %find_lang
with MinGW packages, although the exact usage isn't that obvious. Use it like this:
Name: mingw32-foo %install %find_lang foo %files -f foo.lang