Am Mittwoch, 17. März 2010 schrieb Dominique Leuenberger:
Good day everybody,
Today I have a question regarding the packaging policy. i'm building the package orc (which is the successor of liboil). now, orc is a compiler, called orcc and a bunch of libraries.
The libraries are split in a package according shlib (no problem there). The binary orcc would be in the main package and the -doc contains the extensive documentation.
now the question is mainly with focus on the development headers: Should those really be split in a -devel package? As I see it so far pretty much every package that will require orc compiler will need access to the specific headers (but who know, this might change). The -devel package without the compiler itself is rather useless too I think.
What are your suggestions? 1) Having the devel files in the main package and make rpmlint quiet ? b) Move orcc to the -devel package?
If I look at gcc45 for example this contains a list of header files as well, so I'm very much inclined to do the same for orc (so option a).
Any comments / suggestions / recommendations / objections / [...]ions ?
I packaged it for packman this way: orc (the compiler) liborc-0_4-0 (the libs) orc-devel (header and linklib, and devel-docs) with Requires: orc = %{version}
Dominique
have fun Toni -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org