On Sat, Apr 09, 2005, Shawn Walker wrote:
> I've spent quite a bit of time digging through the OpenPKG handbook looking
> for
> documentation on the specific nuances of OpenPKG rpm spec files. So far, what
> I've found is that the format isn't really documented, and that writing your
> own spec files is done by studying existing examples. Am I correct in this
> assumption?
Yes and no. OpenPKG RPM is 99% compatible with the RedHat RPM. OpenPKG
RPM just has a few additional features added (like additional headers,
sections, etc). So, lots of the RedHat RPM documentation applies just
fine to OpenPKG RPM.
OpenPKG uses just a bunch of additional _local_ macros which are all
named %{l_xxxxx}. These are unfortunately not greatly documented, yes.
OTOH most of them (like %{l_prefix}) are straight-forward to understand
by just looking at an arbitrary OpenPKG .spec file. Some others (like
%{l_platform} and %{l_value}) are more complex and documentation should
still be written. OTOH, you always always always want to start from an
existing .spec file anyway -- especially if you want that the .spec file
is taken over into the official repository at some time in the future.
Because the official OpenPKG .spec files have a _very_ strict syntax
where each indentation, each whitespace and even each missing or
superfluous trailing slash on paths is ensured to be the same across all
over 850 .spec files. This is done by the "openpkg dev lint" command
which all .spec files have to pass before they are comitted to our
CVS. So, my strong recommendation is to write an OpenPKG .spec file,
either use the "openpkg dev new" command (if you have an "openpkg dev"
environment setup) or use a less complex existing OpenPKG .spec file as
the base for your package.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [email protected]
