<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); font-family: Verdana; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Hi,</div></div></div><div><blockquote type="cite" class=""><div class="">On 29 Nov 2017, at 18:05, Mike Marion <<a href="mailto:mmarion@qualcomm.com" class="">mmarion@qualcomm.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Wed, Nov 29, 2017 at 04:54:42PM +0000, Joe Doupnik wrote:<br class=""><br class=""><blockquote type="cite" class=""> Correct, I did not because I am installing a server, not the <br class="">desktop product line.<br class=""> With your suggestion, I have just done a new installation, ticking <br class="">the desktop applications box for this server, and finally the Gnome <br class="">option appears in System Role. Opaque.<br class=""></blockquote><br class="">I actually find this split with SLE15 a lot clearer than the current<br class="">SLES vs SLED or SLES+WE. <br class=""><br class="">I take this move as a sign that Suse also seems to realize that the<br class="">current split between SLES and SLED probably should go away (despite<br class="">there still being SLES and SLED offered). As you mention, most of the<br class="">time the difference seems to be based on arbitrary decisions. Don't get<br class="">me started on how support for SLED vs SLES is done despite them being<br class="">the same code base.<br class=""></div></div></blockquote><div><br class=""></div><div><div>Well if you have unanswered technical question, please ask them here (but let’s </div><div>create a new thread). </div><div><br class=""></div><div>If you have unfulfilled needs for your own use case for SLED, SLES, SLE-WE, </div><div>we can also discuss this privately via <a href="mailto:beta-programs@lists.suse.com" class="">beta-programs@lists.suse.com</a>.</div><div><br class=""></div><div>Last but not least, it is true that all SLE products have the same code base, </div><div>but the devil is in the details, they do not have the same use cases, nor used </div><div>with the same hardware (GPU, display, etc) and they also bring their own </div><div>packages which are not present in other SLE products. </div><div>That’s the general reason why SLED and SLES have different support policy.</div><div><br class=""></div><div>Regards,</div></div></div><br class=""><div class="">--<br class="">Vincent Moutoussamy<br class="">SUSE Beta Program and SDK Project Manager</div></body></html>