Proposal for toolset modifications for LSB-Desktop release

Hello,
       Brief discussion of the issue at hand:
       
       Following tools need to be updated for lsb-desktop release: 
       	Lsbcc
       	Lsb-buildenv
       	Lsbappchk
       	Lsblibchk
       	Lsbcmdchk
       	
       The goal is to avoid having separate version of this tool for
desktop. Here is a proposal to address this problem (from user point of
view)
       
       For each of these tools we will add following command line
option:
       	--target | -T=[desktop,core] with core being the default. So if
no option is specified, target will be set to core.

-M option will remain for each of these tools to keep granularity if
needed.
       
	e.g. lsbcc command line for desktop will look like: lsbcc
-T=desktop and for lsb3.0 there will be no change.


For appchk: we currently have -A option to enable all modules. I propose
to remove that option. For desktop users the usage will be lsbappchk
-T=desktop followed by -L options and binary name.


For Implementation:
Since we do not have LSB product table in the database listing all the
modules for each product (core and desktop), we will hardcode the list
of modules for each target till we fix the DB. So for appchk, libchk the
implementation of -T option will be effectively mapping the tool to
concerned modules for that target. E.g. by default (target set to core),
the tool will work on Core, C++ and Graphics modules; for desktop
target, it will work for Graphics-Ext, Gtk, Qt and XML modules. 

In LSB 4.0 timeframe I propose we add this new table describing cert
products and then the tools can be modified to remove the hardcoded
stuff. 

Thoughts, comments?

Thanks,

-Rajesh