Re: [Lsb-wg] Completing the LSB DB schema
Pradosh Adoni <[email protected]> Mon, 05 Dec 2005 13:01:48 +0530
| Newsgroups | gmane.linux.lsb.test-suite,gmane.linux.lsb.specification |
|---|---|
| Organization | Codito Technologies Pvt. Ltd. |
| Message-ID | <[email protected]> |
--===============2003622220==
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="=-S2hsp249+Of3k9XjnC4Y"
--=-S2hsp249+Of3k9XjnC4Y
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Please treat this call as URGENT.
I'm bringing this to the other lists so that everyone knows about it ...
thanks
-- pradosh=20
On Fri, 2005-12-02 at 08:19 -0800, Wichmann, Mats D wrote:
> General call for help: if you think you understand
> a part of the LSB database schema that *isn't* already
> documented, please update the wiki page (or send
> me the info and I'll update it):
>=20
> http://www.linuxbase.org/LSBWiki/SpecDatabaseSchema
>=20
> I'm trying to make sure we've got this kind of stuff
> well documented so it's easier for new people to
> understand what is needed and so we're better protected
> against knowledge gaps when topic experts move out of=20
> the project.
>=20
> A way to "check your assumptions" is to look in the
> scripts which extract data from the database, and
> see what they're doing. Primarily these are the mk*
> scripts scattered around the cvs tree: in=20
> build_env/headers, in lsbspec, and in tests/misc/*.
> A secondary check is the dbadmin php code - secondary
> because not all of it may have been updated for
> changes, although we *think* it's in pretty good
> shape, especially the admin/ subdirectory.
>=20
> I'm also concerned that we've flagged members no longer
> used. We already know of one instance where a field
> wasn't used any longer because it had moved to a join=20
> table, yet one of the scripts under development was=20
> assuming that field was the place to put the data -=20
> want to avoid any more of that problem.
>=20
>=20
> Here are items that aren't documented:
>=20
> ArchClass.{ACpos, ACvoffset}
>=20
> ArchInt.AIversion
>=20
> ArchTypeMem (table and members)
>=20
> BaseTypes (table and members)
>=20
> ClassInfo.{CIbase,CInumvmitypes,CIflags,CIvcalloffset,
> CIbaseoffset,CIbasevtable,CIlibg,CIvtclass,CInumvtt}
>=20
> DynamicEntries (table and members)
>=20
> ElfSections (table and members)
>=20
> Header.Hlib
>=20
> Interface.Icomment
>=20
> Parameter.{Parsize,Pconst,Pttid,Pnull}
>=20
> ProfLib, Profile (yes, I know these aren't used now)
>=20
> RpmTag.{Rtag,Rcount}
>=20
> Standard.{Stype,Sshort}
>=20
> TestCmd (table and members)
>=20
> Type.{Tarray,Tattribute}
>=20
> TypeMember.{TMsize,TMoffset,TMtypetype}
>=20
> VMIBaseTypes.VBTpos (and table purpose)
>=20
> Vtable.{VTvtpos,VTpos,VTviid} (and table purpose)
> _______________________________________________
> Lsb-wg mailing list
> [email protected]
> http://mail.freestandards.org/mailman/listinfo/lsb-wg
--=-S2hsp249+Of3k9XjnC4Y
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iQEVAwUAQ5Ps5H/NtiPREx7AAQK5RQf/Sbo7BmwVGnpkZJqt+6PIYK4msgpYBB+X
meKQtJH7Id00npbRGOe80mfV9cR+WVHP8wNKOVhsg1adKLaRvS5WencDrow+crAk
3eHJ3WazvcYqX/ZrwCilsznYFVh3LsVleMO7lJvUfAtH0XGHpLYGpIZHVPjM9Iva
keVE8MmCxWq8jWT4FA/FmFWcWkeFs/58ZItzv2PWWqSOrI+eQc0i17l/rB1wIeef
03kxukLpYOjLFx6VBDl+gDKNCm02Q2a/YVj9MC/eBfSJgvWI3MigoYUGR5jK9f3x
i4Cr1c3G3aU5Au9Ae1CTwr1Y+H72HuMKmIRbXXuC+xs7LfuAw1pXzg==
=ISdm
-----END PGP SIGNATURE-----
--=-S2hsp249+Of3k9XjnC4Y--
--===============2003622220==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
lsb-test mailing list
[email protected]
http://mail.freestandards.org/mailman/listinfo/lsb-test
--===============2003622220==--