Jim Walker wrote:
> Danek Duvall wrote:
>> What is the problem you're trying to solve?
>
> We have software that runs the test farm including
> installing systems, zones, ldoms, domus, accounts...
>
> Instead of guessing by picking a random os
> attribute that tells me if I have a nevada
> os or an opensolaris os, I wanted to see if
> the pkg team knows of something in the os
> that identifies it as either being nevada or
> opensolaris that is persistent (ie. I want
> the code to adapt to the os, nevada != opensoalris).
But why do you want the code to adapt - most things should be
the same on both, and with Nevada and OpenSolaris converging
in the future, (or Nevada going away and being replaced by
OpenSolaris depending on your point of view), there should
eventually be no differences at all.
What exactly is it going to do differently with this information?
If it's a specific functionality, why not test for that functionality
instead of assuming you know which derivative is which, and then
breaking when someone makes a new extrusion/distribution which
doesn't match your assumptions?
--
-Alan Coopersmith- [email protected]
Sun Microsystems, Inc. - X Window System Engineering
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
