On Sunday 08 July 2007, Kent Fredric wrote: > Ok, I've re-thought some of my ideas and tried to come up with a more > concise explanation > with some practical example syntax. The basic concept of 'check' was > 'this will work even if the package aint installed yet' and info was > 'for working but bust packages only', but that can be superceded with > a CHECKLIST and a conditional driven INFO function.
as they say, the devil is in the details ...
> pkg_getinfo(){
> if [[ installed ]]; then
> someSelfCheck;
> someSelfCheck;
> echo someversionNumberStuff;
> fi
> someBasicSystemCheckRequiredForPkgToWork();
> if [[ someCondition ]]; then
> get_info( some-cat/d-lib ); # its not on the dep list, but we want
> to check its info status as part of /our/ info status.
> fi
> }
the claim i'm making is that there generally isnt any code/checks worth adding
to ebuilds that would be useful for the purpose of an ebuild diagnosing
itself to determine whether it is broken and how it is broken. we just dont
have a language yet to properly describe the process of diagnosing and fixing
oneself. a fun thesis for an AI doctorate :p
-mike
signature.asc
Description: This is a digitally signed message part.
