Re: [gentoo-dev] automated extended information gathering

[Kent Fredric]

On 7/8/07, Kevin Lacquement <kevin@××××××.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Marius Mauch wrote:
> >
> > 5) considering 3), I'd rather see such information be specified by
> > ebuilds somehow, not a global file (think about overlays). Maybe by
> > installing a script in a specific location or so.
> >
> > Marius
> How about adding another function to the ebuild format?  pkg_getinfo()?
>
> Kevin
>
>

Implementation details wise, I would like to see packages have
possibly 2 functions,
1: Info, and 2: Check.
Reason Being that you wont be able to fetch installation status info
on a package thats not installed, and if a package is failing to
install, you're more likely wanting to check the status of the things
it depends on, not the package itself.

Check would contain manual tests for a given package, thats either
installed or not installed ,as well as names of packages to run info
on.

Info would be more usefull in diagnosing mis-installed packages or
packages that failed to run properly despite being compiled and
installed without a hitch ( it happens )

( These could even be good enough to help the user self-diagnose the
problem, a feature I consider wonderfully intuitive and not in any
other distribution yet ;) )

pkg_check()
{
            if ( uses blah )
            {
                 some_basic_check();
                 pkg_getinfo_installed( x11-wm/blah );
            }

}


I may be on to a good thing, I may  be retarded, but I'd rather
provide something that could be a potentially good thing with the risk
of being retarded than to have hidden that good thing. ;)


-- 
Kent
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x|
print "enNOSPicAMreil kdrtf@×××.com"[(2*x)..(2*x+1)]}'
-- 
gentoo-dev@g.o mailing list