`<div dir="ltr"><div style>We don't package X11 libs in code, because nothing in core needs them to run or build. The core is the smallest self sustainable set of packages.</div><div style><br></div><div style>We encourage the "layered-cake" approach using multiple repos.</div>
<div><br></div>We take that stance because the problem is deeper and more complex than you elude to.<div><br></div><div style>Your vendor ships something that needs X11 libs. But they don't ship OmniOS binaries (if they didn't they'd have no X11 deps). So, what you have instead are likely Solaris binaries. Now, while Solaris 10 and earlier binaries will run on OmniOS, we only guarantee that the system ABIs are stable. X11 is not that. So, in order to run those Solaris 10 binaries that need X11 client libs we have a possible ABI issue. If we were to ship X11 client libs, we may not ship the same ones as with Solaris 10 (we are newer after all), so that binary might explode if you convince it to link against the ones we would have provided. The only way to make sure it works is to copy over the libs from a Solaris 10 box and LD_LIBRARY_PATH them for your app. This has the highest probability of working.</div>
<div style><br></div><div style>I can share our approach to such things, it may or may not help. I have a private IPS repo for my junk. Without own private IPS repo, I concern myself less with the redistribution rights of what I place in there. We take an IPS-or-nothing approach. If I find myself with a piece of software that doesn't have an IPS (tar, installer, etc. etc.). I take a machine and install it, I find all files it provided and create an IPS manifest, I SMF it if it hasn't been and put that int he manifest. I run it, if it doesn't work due to missing libraries, I create a private directory somewhere reasonable and relative to the install path and place the missing shared libraries in there. I add that to the LD_LIBRARY_PATH in the SMF manifest and add the libs to the package manifest.... once it works, I pkgsend the manifest to my server and voila. I know how said piece of software installable via IPS in non-snowflake fashion.</div>
<div style><br></div><div style>I would say, this process is required once in a blue moon.</div><div style><br></div><div style>While I'm sure we all find the need to hack up a piece of software to run on a foreign OS, I'll caveat that hacking a piece of mission critical software to run on OmniOS that isn't shipped for OmniOS is likely easier than hacking your EULA to allow you to do so or hacking your support contract for said software to be valid or useful.</div>
<div style><br></div><div class="gmail_extra">Best regards,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Theo<br><br><div class="gmail_quote">On Fri, May 17, 2013 at 1:34 PM, Bob Friesenhahn <span dir="ltr"><<a href="mailto:bfriesen@simple.dallas.tx.us" target="_blank">bfriesen@simple.dallas.tx.us</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Fri, 17 May 2013, Theo Schlossnagle wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
A few things that might help you our<br>
1) this is not in core by design.<br>
2) using a browser remotely sounds painful... try ssh options to either forward a port (-L) or act as a SOCKS proxy (-D) both<br>
*super* useful.<br>
3) this does not solve your "I can only manage an HBA with a Java GUI issue"... you should burn that vendor's offices down*.<br>
</blockquote>
<br></div>
I have some mission-critical software here from Sun which uses an "Install Shield" type installer on Solaris. I am not sure if the installer is x86/SPARC binaries, or based on Java. Once installed, the software runs headless on a server.<br>
<br>
There is other software (useful on servers) where use of X11 is optional at run-time yet the binaries will fail to run if the X11 libraries are missing. If the X11 libraries are missing, then it is necessary to create a special build of the software and commonly-available pre-compiled binaries won't work.<br>
<br>
Basic X11 client libraries and support files (all highly-portable stuff) seems like a basic requirement. This is quite different than an X11 server, which has substantial hardware dependencies.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
4) There are people using Joyent's pkgsrc work to build X libs.<br>
</blockquote>
<br></div>
That sounds helpful.<span class="HOEnZb"><font color="#888888"><br>
<br>
Bob<br>
-- <br>
Bob Friesenhahn<br>
<a href="mailto:bfriesen@simple.dallas.tx.us" target="_blank">bfriesen@simple.dallas.tx.us</a>, <a href="http://www.simplesystems.org/users/bfriesen/" target="_blank">http://www.simplesystems.org/<u></u>users/bfriesen/</a><br>
GraphicsMagick Maintainer, <a href="http://www.GraphicsMagick.org/" target="_blank">http://www.GraphicsMagick.org/</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>
<p>Theo Schlossnagle</p>
<p><a href="http://omniti.com/is/theo-schlossnagle" target="_blank">http://omniti.com/is/theo-schlossnagle</a></p>
</div></div>
`