New python build process for "bundled" python modules

[Carsten Grzemba]

could be a special category ("default with a package with python binding") a solution. So that we can handle 
the packages called py_ separately? 

Am 05.02.14 schrieb Dagobert Michelsen  <dam at opencsw.org>:
> Hi folks,
> 
> I just noticed
>  https://www.opencsw.org/mantis/view.php?id=5144
> where python modules bundled with other things not being built with the python category
> do not have the new python-specific layout and modulations. Has anyone a good idea on
> how to fix this? My suggestion would be to make a separate recipe just for the python
> module using python category and the included modulations but override the build process
> to use standard configure. But I don’t like the solution as it requires a copy of the
> recipe. Categories as facets of a build would be nice but I don’t have a smart idea
> on how that should be integrated best.
> 
> 
> Best regards
> 
>  — Dago
> 
> -- 
> "You don't become great by trying to be great, you become great by wanting to do something,
> and then doing it so hard that you become great in the process." - xkcd #896
> 
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20140205/de46172c/attachment.html>