2008/11/1 Dagobert Michelsen <span dir="ltr"><<a href="mailto:dam@opencsw.org">dam@opencsw.org</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style=""><br><div><div><div><blockquote type="cite"><div class="gmail_quote"><div><span style="font-family: verdana,sans-serif;">Still, this is completely the right way to go IMHO. I'll try and get my packages in there.</span></div>
</div></blockquote><div><br></div>This will be done automatically once we have single package</div><div>checkout in GAR. Auto-build on commit :-)<br></div></div></div></div></blockquote><div><br><span style="font-family: verdana,sans-serif;">Yay! Exactly the way it should be. :)</span><br style="font-family: verdana,sans-serif;">
<span style="font-family: verdana,sans-serif;"> </span><br style="font-family: verdana,sans-serif;"></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style=""><div><div><br><div> Personally, I think OpenCSW has the</div><div>moral right to stick to /opt/csw</div></div></div></div></blockquote><div><br style="font-family: verdana,sans-serif;"><span style="font-family: verdana,sans-serif;">Having the moral right is all well and good, but it is not pragmatic to use /opt/csw indefinitely.</span><br style="font-family: verdana,sans-serif;">
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style=""><div><div><div></div></div><div>The question is: will the maintainers here will accept leaving the</div>
<div>prefix to Blastwave and start with a new one.</div></div></div></blockquote><div><br style="font-family: verdana,sans-serif;"><span style="font-family: verdana,sans-serif;">I could be wrong, but I guess most maintainers want it somewhere in /opt that no-one else is using.</span><br style="font-family: verdana,sans-serif;">
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style=""><div><div></div><div><br></div><div>Apart from that it would be cool to allow customized package trees</div>
<div>with different suffixes (e. g. like optimized trees for T1/T2).</div><div>However, that would impose quite an extra amount for package</div><div>maintainers (not for all, but there are nasty ones).</div></div></div></blockquote>
</div><br><span style="font-family: verdana,sans-serif;">If we get everything in GAR, and automated builds, lots of stuff becomes loads easier.<br><br>Gary<br style="font-family: verdana,sans-serif;"></span><br style="font-family: verdana,sans-serif;">
<span style="font-family: verdana,sans-serif;">-- </span><br style="font-family: verdana,sans-serif;"><font size="1"><span style="font-family: verdana,sans-serif;">Gary Law</span><br style="font-family: verdana,sans-serif;">
<span style="font-family: verdana,sans-serif;"><a href="mailto:glaw@opencsw.org">glaw@opencsw.org</a></span></font>