Brian,Chandler includes all of the third-party packages the way it does for a couple of reasons:
1) at the time Chandler was starting many of the third party libraries had existing bugs that needed to be patched in order for Chandler to work and 2) it was an early design decision that given #1 above that Chandler be made as easy to install as possible.
Since to solve #2 in the presence of #1, and not that all this was being worked/decided on almost two years ago, to ensure that we have access to the proper versions of the libraries we would build and include the libraries in our own tree.
Lately a lot of the third-party products have made progress to fixing the bugs/issues we are having so it has been an item on my Todo list to re-visit the idea that Chandler could be built to depend on certain versions of third-party packages but I have not gotten to that point yet.
The build notes for Debian are rather sparse as basically they cover only what is needed to get the Chandler make environment running.
I use at home and work both Debian and Ubuntu so I would be more than happy to work with you on any questions or changes to the build system that make sense for us.
--- Bear http://code-bear.com Build and Release Engineer Open Source Applications Foundation (OSAF) http://www.osafoundation.org PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29 On Jun 13, 2005, at 9:43 PM, Brian Thomason wrote:
Hi,I'm looking to create Debian packages of Chandler for Linspire and have run into some concerns. It appears that in the external folder, chandler includes third party software such as wxwidgets, python, etc... It has proven difficult to compile chandler using existing, packaged versions of these pieces of software.My question then is twofold:1.) Why is the chandler build process such as it is? It seems overly complex. 2.) Has anyone attempted creating Debian packages of Chandler before, that build against system libraries and not those automtaically downloaded and statically compiled in?I read the build notes for Debian, but they were sparse and dated.I'd really like to see this in our repository, so any help would be greatly appreciated. Thanks for your time.-Brian _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
PGP.sig
Description: This is a digitally signed message part
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
