On Jan 9, 2008, at 8:35 AM, Alexander E. Patrakov wrote:

> 2008/1/9, Jeff Johnson <n3npq@mac.com>:
>>      %_use_internal_dependency_generator 0
>
> This worked, but produced dependencies on libc.so.6 and friends in the
> resulting RPM (and lsbpkgchk doesn't like them, so I had to add
> AutoReqProv: no to the spec file).
>

Yep. Sorry for not mentioning. There's likely some slightly better
means than AutoReqProv: no that should be done, but AutoReqProv
is one way to disable dependency extraction.

Better would be to insturment custom lsb-find-provides and lsb-find- 
requires with
actual tests of, say, permitted file paths and content, and emit
     Requires: lsb
iff the tests pass. E.g. many FHS tests could easily be done  
automagically
on every build.

>>      %_build_file_context_path       %{nil}
>
> No effect, the tag 1147 (RPMTAG_FILECONTEXTS) is still there (with  
> Debian).
>

That smells like a bug in rpm.

No matter what, all this stoopid configgery to produce a LSB "standard"
package could be simplified to a --lsb option in rpm if anyone cared to
ask me to implement.

No one has.

But I do ask the question:
     What use is rpm as a LSB "standard" format if everything in  
rpmbuild needs disabling?
     Isn't cpio or tar or ... a better choice than a lobotomized  
rpmbuild?

73 de Jeff