<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi</div><div><br>On 8 Sep 2013, at 18:36, Aurélien Larcher <<a href="mailto:aurelien.larcher@gmail.com">aurelien.larcher@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div><div><div><div>Hi everyone,<br></div>since the numpy python package available in hipster seems broken (segfaults), I installed the latest stable 1.7.0 compiled with gcc, without a linear algebra backend.<br>
</div>So I intend to add latest numpy, scipy (and atlas for the backend) in oi-userland if it is ok.<br></div></div></div></div></blockquote><div><br></div><div>Just fork the repository, commit things and create a pull request. I will pick it up and merge.</div><br><blockquote type="cite"><div><div dir="ltr"><div>How does it fit in the way python modules are packaged ? Should they be added to the python folder ?<br></div>
<div>Should 32 bit and 64 bits be both provided or only one of them ?<br></div></div></div></blockquote><div><br></div>At the moment, OI has only python 2.6, which sucks. Therefore, I am working on bringing new pkg, which is needed for publishing python 2.7. Once that gets published, plan is to make it the default version.<div><br></div><div>Speaking of packaging look at any python component. It should reside under python directory, There should be 2 p5m files (e.g numpy.p5m and numpy-26.p5m, numpy.p5m creating conditional dependency on a numpy-26. Just ignore -PYVER.p5m for now).</div><div><br></div><div>Bitness is something packager has to consider. If there is a point in delivering a 64 bit package, then do so. </div><div><br><blockquote type="cite"><div><div dir="ltr"><div><br></div><div>What about gdb, is it possible to upgrade to 7.x to get python extensions or are there any known showstoppers ? (I installed the latest gdb with the 'historical' patches).<br></div></div></div></blockquote><div>I have looked at gdb yesterday and the component needs removing studio specific compile flags and make it builadble by gcc. Also test suite should pass all tests if possible to test package functionality.</div><div><br></div><blockquote type="cite"><div><div dir="ltr"><div>
I have also a few numerical libraries pending that I converted from my SFE specs. <br></div></div></div></blockquote><div><br></div>Great, if you mind sharing just create a pull request.</div><div><br></div><div><blockquote type="cite"><div><div dir="ltr"><div>Best regards,<br></div><br>Aurelien<br clear="all"></div></div></blockquote><div><br></div>Cheers,</div><div>Adam<br><blockquote type="cite"><div><div dir="ltr"><div><div><div><div><div><div><div><div><br>-- <br><font style="font-family:courier new,monospace" size="1">-------------------------------------------------------------------------------<br>
LARCHER Aurélien | KTH, School of Computer Science and Communication<br>
Work: <a value="+4687907142">+46 (0) 8 790 71 42</a> | Lindstedtsvägen 5, Plan 4<br>Mob.: <a value="+46709464017">+46 (0) 7 09 46 40 17</a> | 100 44 Stockholm, SWEDEN<br>-------------------------------------------------------------------------------<br>
Praise the Caffeine embeddings ...</font>
</div></div></div></div></div></div></div></div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>oi-dev mailing list</span><br><span><a href="mailto:oi-dev@openindiana.org">oi-dev@openindiana.org</a></span><br><span><a href="http://openindiana.org/mailman/listinfo/oi-dev">http://openindiana.org/mailman/listinfo/oi-dev</a></span></div></blockquote></div></body></html>