<feed xmlns='http://www.w3.org/2005/Atom'>
<title>multitech-oe.git/classes/python-dir.bbclass, branch org.openembedded.dev</title>
<subtitle>Multi-Tech CoreCDP 1.x OpenEmbedded Tree</subtitle>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/multitech-oe.git/'/>
<entry>
<title>python-dir: raise an Exception instance, not a string</title>
<updated>2010-05-19T19:53:49+00:00</updated>
<author>
<name>Chris Larson</name>
<email>chris_larson@mentor.com</email>
</author>
<published>2010-05-19T16:39:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/multitech-oe.git/commit/?id=16d2cc32574aecceff630adab0d9a36d4fa5e568'/>
<id>16d2cc32574aecceff630adab0d9a36d4fa5e568</id>
<content type='text'>
Signed-off-by: Chris Larson &lt;chris_larson@mentor.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Signed-off-by: Chris Larson &lt;chris_larson@mentor.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>distutils-common-base: move Python dir detection to separate class</title>
<updated>2010-03-25T06:28:25+00:00</updated>
<author>
<name>Roman I Khimov</name>
<email>khimov@altell.ru</email>
</author>
<published>2010-03-23T10:27:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/multitech-oe.git/commit/?id=e0f9409803d6edc14608828967c0c52b5a2d182e'/>
<id>e0f9409803d6edc14608828967c0c52b5a2d182e</id>
<content type='text'>
Allows to inherit that in packages containing Python extensions but still tightly
control packaging of those extensions. Mainly for the cases where you want
those python modules/extensions/parts to be packaged separately from the main
package in order not to introduce python dependency where you don't need it.
Technically, you can do it with distutils-common-base, but it might require
more FILES_* work than with python-dir.

Introduce PYTHON_SITEPACKAGES_DIR along the way, site-packages directory is
referenced frequently enough within class files, but some recipes also pack this
directory as

${libdir}/python2.5/site-packages
${libdir}/python2.6/site-packages
${libdir}/python*/site-packages
/usr/lib/python*/site-packages
${libdir}/*/site-packages

all of which are not perfect.

Signed-off-by: Roman I Khimov &lt;khimov@altell.ru&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Allows to inherit that in packages containing Python extensions but still tightly
control packaging of those extensions. Mainly for the cases where you want
those python modules/extensions/parts to be packaged separately from the main
package in order not to introduce python dependency where you don't need it.
Technically, you can do it with distutils-common-base, but it might require
more FILES_* work than with python-dir.

Introduce PYTHON_SITEPACKAGES_DIR along the way, site-packages directory is
referenced frequently enough within class files, but some recipes also pack this
directory as

${libdir}/python2.5/site-packages
${libdir}/python2.6/site-packages
${libdir}/python*/site-packages
/usr/lib/python*/site-packages
${libdir}/*/site-packages

all of which are not perfect.

Signed-off-by: Roman I Khimov &lt;khimov@altell.ru&gt;
</pre>
</div>
</content>
</entry>
</feed>
