Hello Denis, I just came back to updating the Salomé package in alioth, but I forgot about these emails. So although my work is based on your earlier patches, I'm afraid I may have re-done some of the work you already did in your repository, but did it differently. I apologize for that.
The package in alioth should build now. For each module, it creates a separate build tree, reconfigures, configures, compiles and installs, then removes the build tree. This should reduce the disk space required for compilation by quite a lot. So the only things remaining for the -10 release are this python module issue (below) and reorganizing the binaries. I'll look at your wip-python repository branch for the former, and will take a stab at the latter, based on the division proposed earlier in this bug. Then we can move on to porting the patches to 5.1.4 (or current upstream git), and shrinking and reorganizing the documentation... -Adam On Thu, 2010-06-17 at 09:25 +0200, Denis Barbier wrote: > On 2010/6/16 Adam C Powell IV wrote: > [...] > > I think the release goals for -10 should be as follows: > > * This change for faster development > > * Separate build tree(s) as you implemented before in a patch > > * Split the package as described above (plus salome-dev) > > * Bug fixes already in alioth > > Sounds good? Any others? I think this is doable by the end of next > > week. > > The salome package contains many files /usr/lib/salome/lib/_lib*.so > which are not libraries but python modules, and must thus be installed > elsewhere in order to be loaded by python. I started working on this > issue, see the wip/python branch in my repository. -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/
signature.asc
Description: This is a digitally signed message part
