<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Yes that's how I've ended up packaging all of the Raptor components (via the Open Build Service). Everything installs to /opt/raptor/* - including the bundled Jetty. The only thing that lives outside of /opt/raptor is the initscript. So agree with your way of thinking :-).<div><div><br></div><div>R.<br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">--<br>Dr Rhys Smith: Identity, Access, and Middleware Specialist<br>Cardiff University & JANET(UK)<br><br>email: <a href="mailto:smith@cardiff.ac.uk">smith@cardiff.ac.uk</a> / <a href="mailto:rhys.smith@ja.net">rhys.smith@ja.net</a><br>GPG: 0xDE2F024C<br></span>
</div>
<br><div><div>On 3 Nov 2011, at 11:37, Chad La Joie wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>So, while waiting for things to compile and other busy work, I've been<br>kicking around the idea of how we might package IdPv3 (and other<br>upcoming Java code) for use with Linux and its package managers.<br>Here's my thoughts on this so far.<br><br>We should package the code as RPMs and DEBs. This will make it easier<br>for people to keep up to date with releases.<br><br>We can not use the "standard" Unix filesystem layout. There are two<br>main problems that I see in attempting to do so. It would be<br>impossible to install different IdP versions at the same time because<br>you'd end up with different lib versions being installed in the same<br>directory and thus on the classpath together. That is going to be<br>very problematic for people who do IdP hosting. Second, the unit of<br>management within Java (at least for our webapps) is the WAR, which<br>includes libraries (which presumably would be expected to go in to<br>/usr/lib somewhere) as well as various other files (e.g., images, text<br>files like CSSs, conf files like web.xml). Those other things really<br>shouldn't go in the /usr/lib directory but do need to be in the same<br>directory structure as the libs in order to be deployed. In short,<br>the Java environment makes assumption that are different than the ones<br>the Linux environment makes.<br><br>So, at this point, I think the RPM/DEB packages are just going to<br>install/update the IdP in a /opt/shibboleth-idp directory that looks<br>mostly like it does today.<br><br>-- <br>Chad La Joie<br><a href="http://www.itumi.biz">www.itumi.biz</a><br>trusted identities, delivered<br>--<br>To unsubscribe from this list send an email to dev-unsubscribe@shibboleth.net<br></div></blockquote></div><br></div></div></body></html>