Conf. call Thursday
"Wichmann, Mats D" <[email protected]> Wed, 12 May 2004 15:44:52 -0700
| Newsgroups | gmane.linux.lsb.implementation |
|---|---|
| Message-ID | <[email protected]> |
Same LSB time, same LSB number .... Some interesting tasks, I'd like to finish up this list, file bugs where we need, and start tracking. Please ADD to this list in advance of the meeting, if possible: send me updates, send a revised list, whatever. I'm SURE there's stuff missing. Add bug numbers if you happen to know them. lsbsi -> beta: ===================== s390x broken build do we need nptl / new glibc / new binutils? cmdchk-reverse cleanup library cleanup lib -> lib64: done everywhere? test fails (LOTS on some platforms, less on others) lsb-release 2.0 (cmd-line info tool) lsbsi-lsb 2.0 (rpm initializer pkg) completing the UML cross-test with appbat appbat -> beta: ================ is lib64 necessary under /opt/whatever? package names install location shared libs that include static libs (broken) Module dependencies 2.0 FVTs (certification) cross-test on lsbsi build tools -> beta: ==================== libbat - does it all need to be PIC? Does it need more libs to solve appbat-shared-libs question? package names validate pthread_nonshared are there interfaces in multiple libs? C++ header package Don't plan to issue chroot at this time - resource crunch check tools -> beta: ==================== libchk looks ready appchk bug scrub how close is dynchk? work still needed on package checkers (package format, package install) common package issues: ====================== 2.0 dependency (lsb-foo-<arch> or lsb-foo?) need standard specfile bits - what header tags with what values (distributor, Packager, License, etc) insuring buildability: arch translate, terminate build, etc.