<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi!</div><div><br></div><div>(Sorry for top-quote, but on mobile...)</div><div><br></div><div>Copy that and FHS states this quite clear. Personally I'm also not a huge fan of software installing to /opt.</div><div>Neither am I a fan of packaging (local) libraries in there - for a variety of reasons. I even think the Fedora packaging guidelines forbid this.<br><br>-of (mobile)</div><div><br>Am 05.06.2015 um 17:17 schrieb Michael Stahnke <<a href="mailto:stahnma@puppetlabs.com">stahnma@puppetlabs.com</a>>:<br><br></div><blockquote type="cite"><div><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 5, 2015 at 8:15 AM, Michael Stahnke <span dir="ltr"><<a href="mailto:stahnma@puppetlabs.com" target="_blank">stahnma@puppetlabs.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Fri, Jun 5, 2015 at 6:31 AM, John Florian <span dir="ltr"><<a href="mailto:john.florian@dart.biz" target="_blank">john.florian@dart.biz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Fri, 2015-06-05 at 01:12 -0400, Nico Kadel-Garcia wrote:<br>
> On Thu, Jun 4, 2015 at 2:21 PM, John Florian <<a href="mailto:john.florian@dart.biz" target="_blank">john.florian@dart.biz</a>> wrote:<br>
> > I’ve been curious how Fedora plans to tackle inclusion of Puppet 4, but<br>
> > haven’t heard even a peep on the subject. As described[1], they’ve moved to<br>
> > an all-in-one packaging process that “includes Puppet 4, both Facter 2.4 and<br>
> > CFacter 0.4, the latest Hiera and Mcollective, as well Ruby 2.1.5, OpenSSL<br>
> > 1.0.0r, and our gem dependencies.” Furthermore, “the package installs into<br>
> > its own area in /opt/puppetlabs”. Thus upstream is both bundling and using<br>
> > very Fedora-unfriendly file locations. L<br>
><br>
> As long as it's in "/opt", what's the problem? That's what /opt is<br>
> for! Unwielding and resolving individual components of an integrated<br>
> tool suite is often a nightmare, which is why puppet, chef, and<br>
> numerous commercial packages do the same thing.<br>
<br>
</span>Packaging Guidelines for one. My personal belief is that /opt should<br>
only be populated by the local admin, never the distro nor a vendor.<br>
Personally I do so using a scheme like /opt/$VENDOR/$PRODUCT/$RELEASE,<br>
but to my knowledge the FHS has never ratified anything like that. The<br>
FHS seems to take a rather vague stance on /opt overall IMHO.<br></blockquote></span></div></div></div></blockquote><div><br></div><div>Could functionally explain the difference then between /usr/local and /opt? Opt has been for thrid-party/commercial/optional software for as long as I've used *NIX. /usr/local more for the local admin to build/compile/setup what he/she would like. </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span><font color="#888888"><br></font></span></blockquote></span><div>Just as a point of record, we do /opt/$VENDOR/$PRODUCT </div><div><br></div><div>not so much with the release, but we're close to what you wanted.</div><div><br></div><div> </div></div></div></div>
</blockquote></div><br></div></div>
<pre>-- <br>
devel mailing list<br>
<a href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/devel">https://admin.fedoraproject.org/mailman/listinfo/devel</a><br>
Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct">http://fedoraproject.org/code-of-conduct</a></pre></div></blockquote></body></html>