On 2/16/02 at 6:20 AM, Mike Noyes <[EMAIL PROTECTED]> wrote: > At 2002-02-16 05:42 -0800, Mike Noyes wrote: > >At 2002-02-16 07:25 -0600, David Douthitt wrote: > >>On 2/15/02 at 10:15 PM, David Douthitt <[EMAIL PROTECTED]> wrote: > >> > >> > Perhaps what we NEED is a test suite - a sort of > >> > minimalist "autoconf" which details what works and what > >> > doesn't... > >> > >>Like this: > >> > >>Checking for busybox date.... no > >>Checking for busybox install.... no > >>Checking for ip... yes > >>Checking for netstat... no > >>Checking for route... no > >>Checking for ifconfig... no > >> > >>...etc... > > > >David, Would it be possible to apply something like this > >to package testing. > > Scratch the question above and replace it with: > > Would it be possible to parse the autoconf output above > for package testing?
I wasn't talking about actually USING autoconf... > > e.g. > > Checking package file structure: OK Anyway, apkg -v already does this... > >Checking for program name: foo.bar > >Checking for program version: 1.00 > >Checking for libc version: 2.1.3 Checking for program version requires a way to find it out. Not only that, it implies that if you need 1.00 but have 2.01a_Beta3 then you're alright - but try to program that... Finding the libc version is probably limited to checking the filename in /lib - but is limited again in the comparison values... > >Checking compatibility with Bering... > > Parsing Bering autoconf output: no > > >Checking compatibility with Dachstein... > > Parsing Dachstein autoconf output: no > > >Checking compatibility with Oxygen... > > Parsing Oxygen autoconf output: yes > > >Checking compatibility with PacketFilter: no > > Parsing PacketFilter autoconf output: no > > >Checking compatibility with WRP: no > > Parsing WRP autoconf output: no I was thinking one would run this script in a LEAF environment - and it would be set up by a developer, who defines what is needed. Then you could boot Oxygen (or PacketFilter, or...) and run this script which tests the environment. Now if you could just generate this set of (command) requirements (and option requirements) on the fly from a script.... -- David Douthitt UNIX Systems Administrator HP-UX, Unixware, Linux [EMAIL PROTECTED] _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
