On Jun 21, 2008, at 1:17 PM, Denis Washington wrote:
On Sat, 2008-06-21 at 13:01 -0400, Jeff Johnson wrote:
OTOH, RPMTAG_FILESTATES is gonna matter a _LOT_. So
will leaving stale locks, and forgetting to attach stderr when
your widdle daemon forks.
Could you explain what should go in RPM_FILESTATES? It's not listed in
the LSB specification.
Zeros are same as RPMFILE_STATE_NORMAL and will suffice.
What is primarily important is that the tag exists (so the pointer
does not go NULL),
and that the memory is sized correctly (array of unsigned character
#files is the dimension).
RPMFILE_STATE_NORMAL is what most files have attached.
Until one starts to get into multilib, another UNSPECIFIED area
that will affect ISV's that the LSB "Berlin API" is worfully silent on.
Ditto SELinux, but most of thiose issues are outside of RPM
packaging these days. That can/will change if "modular"
rather than "monolithic" SELinux policy ever succeeds.
Hmmm, you have not included any scrtlets in you _register_package()
methods. AFAIK from listening to Ted T'so, the ability for an
ISV package to run scriptlets is an important need.
Of courrse the "Berlin API" is woefully silent on how to include
scriptlet actions, and how/when those scriptlets should be run.
Again, LSB has no concept of file states before/during/after install,
and has never cared to specify any RPM tag contents that were not
of interest to the "LSB package format" that they have chosen to adopt
from RPM and doggedly persists in continuing into the future of Linux.
73 de Jeff
______________________________________________________________________
RPM Package Manager http://rpm5.org
LSB Communication List rpm-lsb@rpm5.org
