> > can you add these informations into the wiki page. so I will avoid to ask > > again and again. > > I know myself ;). then it would be possible to point upstream to the wiki > > page. > I'll update the wiki page.
thanks > > all this to avoid building a build system on our own. > Yeah I know it's frustrating isn't it.. No, the main point is to work in collaboration with the upstream, understand their choices even if you do not agreed with their choices, and at the end, they need to thrust us when we propose patches which will (at the end) enlarge the community of their users. it can take a long time but it is always rewarding to see a package integrated in the main archive. so use their build system, send patches with did not change their defaults. that way they will understand that we try to build cctbx with them an not against them :) As I understand we will have to provide a --use-system-library option to avoid compiling thoses boos_python etc... bundeled libraries. and also to integrate a few of their patches in the other upstream libraries like libcbf ... Cheers Fred Ps: It took me 2/3 year before my tango package got accepted in the main repository. Indeed it was ready a long time before, but at the end the upstream is quite happy that its software can be installed that easily. apt-get install tango-db -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/a2a20ec3b8560d408356cac2fc148e53568eb...@sun-dag1.synchrotron-soleil.fr
