Re: Announcing the LSB-OS test suite beta
Albert
Appropriate configuration in our announcement meant
the configuration file used by the testsuite, which is provided
with the tests. The procedure is in the readme, we are working
on updating the LSB-OS installation procedure to be like
the other testsets we have, i.e. to be automated so the user
does not need to intervene manually.
Some dependencies I have noted in the past were using byacc and pax (not sure
if we still depend on those). The current setup uses the loopback
device and there were some problems reported with that in some
of the 2.4 kernels.
We could definitely log the packages at the start of the run.
I'll ask Chris Yeoh if we can add that capability to our
master setup scripts that handle the auto installation and
running of the test suite.
regards
Andrew
On Apr 10, 4:48pm in "Re: Announcing the L", Albert den Haan wrote:
> What are the specific "appropriate configurations" of Red Hat and Debian
> unsupported releases which you ran your tests against?
>
> The LSB packaging taskforces will need this information soon for our
> reference implementations on those distributions.
>
> Would logging the packages installed be possible at the start of your test
> runs? The commands to do so are package manager specific, but a simple "if
> [ -x /usr/bin/dpkg ]" should be enough to select amoung them for the short
> term.
>
> For Debian releases: running
> dpkg --get-selections
> will grab a snapshot of the installed modules.
>
> For RedHat releases:
> rpm -qa
> will do the same.
>
> Much more focused lists could be generated by looking for the packages that
> contain the commands and ABI entities needed, but the tool(s) to do that
> have not been (completely) written yet.
>
> Albert
>
Reply to: