Re: Base distro + Requirements definition

[Bruce Robert Pocock <brpocock 10east com>]

On Tue, 2002-06-25 at 11:48, Karl Trygve Kalleberg wrote:

> On 25 Jun 2002, Bruce Robert Pocock wrote:

> > (2) Ability to verify state of installed package?
> >   i.e. check MD5sums & permissions of all package-owned files,
> >    and ability to tell which of them are (config|var) files and 'should'
> >    change under normal usage.
> 
> md5sum and timestamp check. no permissions and owner check, knows which
> are config files, based on directories (policy dictates that all
> configuration files should go into known configuration directories).
> 
> The checking for internal consistency among all packages is a bit lacking
> currently, but is being worked frantically upon. (Ie, you should be warned
> when unmerging a package that has dependants).
> 
> > (3) Ability to identify documentation for a package?
> >   (this goes back to a RFE I have out on scrollkeeper, for users to say
> > "tell me who owns this window, hunt down its executable, and then show
> > me all the associated documentation" - "Click on any window to find help
> > on that program" - analogous to "rpm -qldf /usr/bin/whatever")
> 
> Policy dictates where documentation should go, and its layout, so it can
> be identified.

This particular feature would dep. on being able to trace back to
"package owning file x" (e.g. "rpm -qf x") - I know in e.g. RPM the
"extra docs" are /usr/[share/]doc/x-v.v, (e.g. package-1.0), but rpm -qf
returns just "package," so it's easiest/best to do "rpm -qld package" to
be sure; also saves scanning ( /usr/share/doc/package-*
/usr/share/man/man? /usr/X11R6/share/man/man? ) and various other "help"
locations e.g. GNOME Help...

Probably this all boils down to careful application/integration of
Scrollkeeper, though.