Hi John,
On Mon, 2007-10-22 at 11:32 -0700, John Plocher wrote:
> My impression is that Indiana and Jericho will be built with the
> distro constructor, which is fed a recipe and outputs a distro.
>
> This is why I proposed the idea of branding being associated with
> installer recipes - so we can put our efforts towards defining a
> set of them that have the "right" granularity, size and scope.
That sounds fair to me.
> Making a leap of faith, I assert that the various Distro recipes
> need to look like (pseudo-code):
>
> #define DISTRO "Indiana"
> #include "OpenSolaris-Core.recipe"
> #include "Indiana-private-stuff.recipe"
> #include "Indiana-cool-stuff.recipe"
> #include "OpenSolaris-GNOME-Desktop.recipe"
Nicely put - does this mean that we could have:
#define DISTRO "OpenSolaris"
#include "OpenSolaris-Core.recipe"
EOF
- being that the only thing that's allowed brand itself as OpenSolaris
is the distro that's made from the single core recipe and nothing else.
Putting on a marketing hat (yeah, like I have one) I still see the
worrying idea of people going to opensolaris.org, looking for a thing
called OpenSolaris, seeing the above, downloading it and realising that
it doesn't really look that hot due to it's minimal nature.
*Unless* of course we prepare them for that potential disappointment,
and let them know that after installation they can then simply "pkg add"
their way to their own view of OpenSolaris nirvana ?
That way, we'd get a distro called "OpenSolaris" on opensolaris.org, and
everyone would be happy ? (particularly their ISP, with all the extra
bandwidth usage :-)
Not sure about the user experience, but would this work ?
cheers,
tim
> #define DISTRO "Jericho"
> #include "OpenSolaris-Core.recipe"
> #include "Jericho-private-stuff.recipe"
> #include "Indiana-cool-stuff.recipe"
> #include "OpenSolaris-GNOME-Desktop.recipe"
> #include "OpenSolaris-StarOffice.recipe"
> #include "OpenSolaris-JavaSE.recipe"
> #include "OpenSolaris-NetBeans.recipe"
>
>
> #define DISTRO "Schillix"
> #include "OpenSolaris-Core.recipe"
> #include "Schillix-private-stuff.recipe"
> #include "OpenSolaris-KDE-Desktop.recipe"
> ...
>
> The OpenSolaris Community (probably thru the OpenSolaris ARC)
> defines the recipes that reside in the "OpenSolaris-___" namespace,
> and the branding/trademark guidelines somehow use that namespace in
> their requirements. In other words, it is the OpenSolaris-___ recipes
> that define compatibility across distros.
>
> In some sense, you can only claim to be OpenSolaris Compatible if your
> distro's recipe includes "OpenSolaris-Core.recipe".
>
> -John
> _______________________________________________
> advocacy-discuss mailing list
> advocacy-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/advocacy-discuss
--
Tim Foster, Sun Microsystems Inc, Solaris Engineering Ops
http://blogs.sun.com/timf
