Milan Jurik writes:
> That is truth, of course. But I have two problems with it:
> 
> a) OpenSolaris distro is not ARCed and I did not see it as requirement
> of ON C-team yet (who else passed such thing?).

Good point.  However, in the message you were previously citing, where
I listed these things that should be tested, I went out of my way to
explain that *if* this were *my* project, then those are the things
*I* would want to test.  And I also explained that testing
requirements are a project team responsibility.

Thus, there's no formal requirement here as such, and C-teams and ARCs
don't come into it at all.

> b) do we have some clear documentation how to do it? For bfu/LU we have
> it available.

That's why I suggested asking the team.

The minimum I would try would be installing OpenSolaris, copying over
the binaries, and then doing a pkg image-update and making sure that
flies.

> For these reasons I will welcome help from OpenSolaris distro team (the
> same for all other distros) - if they are afraid of such thing, we can
> give them all data they will request. But we cannot test all distros
> depending on this change. Yes, we should pass as much as possible amount
> of testing. But we need infrastructure and manpower for it.

The general rule for testing is that you're done when you can no
longer think of useful ways to test it, not when you run out of money
to do it.

  http://opensolaris.org/os/community/on/dev_solaris/

But, again, it's your responsibility, so you make the call.

> > I don't think that's true.  Don't ON packages deliver shell scripts
> > used by SMF to /lib/svc/methods/?
> > 
> 
> But those will be tested by LU also. I mean those postrun scripts which
> are outside of ON gate and are OpenSolaris distro specific.

Plus or minus any differences that may exist between OpenSolaris and
SX:CE, such as the existing class action and packaging bits that need
to be run "some other way" on OpenSolaris.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

Reply via email to