Re: Definition of "product" for the purposes of the LSB

Jeff:

When I read this, (and granted I have not taken a lot of time to think
about it), I had questions pop into my mind about if the third party
could really certify the product and be expected to stand behind it.
If one looks at this from a legal support viewpoint, if the third party
had to rely on things not changing under them by those supplying the
original distribution, could they or should they be held accountable.
Certification currently requires the party that does the certification
stand behind their runtime environment and fix problems if and when
they are encountered. It seems this could have the pontential of
creating a lot more problems to police.

I'm not saying one way or another how I will end up deciding on this
question, just that there should be some careful thought go into its
consideration.

Doug

On Tue, Dec 30, 2003 at 11:50:23AM -0500, Jeff Licquia wrote:
> Let's suppose that someone produces a potential LSB Runtime Environment 
> that is not certified, and that has some deficiencies.  This 
> environment's installation system allows for "supplemental media" to be 
> provided at install time for the purposes of fixing bugs, installing 
> add-on software, and so on.
> 
> Let's also suppose that a third party produces "supplemental media" 
> usable by the original Environment's installer which contain fixes for 
> the deficiencies in the LSB Runtime Environment.  With these fixes 
> applied, the Environment is now suitable for certification.
> 
> Would the combination of the original media and the supplemental media 
> be distinct enough to qualify as a separate product, or must the third 
> party generate new media with a new installer and with the fixes 
> integrated onto the media?  Or is there some other way for the third 
> party to achieve LSB certification for the combined Environment?
> 
> _______________________________________________
> lsb-discuss mailing list
> [email protected]
> http://freestandards.org/mailman/listinfo/lsb-discuss

-- 
Doug Beattie
[email protected]