From: Roger B. <ro...@ro...> - 2006-04-28 07:24:33
|
> Among other things, such a source rpm package > would have at least in theory shown me the proper build process and I'd > plan on using the package later for my fiancée (x86_64 arch). There is no build process. Python is an interpretted language. What we distribute is a self-contained bundle of a Python interpretter, shared libraries and the BitPim bytecode. (The latter is an optimisation - the .py files would work just the same). The ordinary x86 "binary" will work fine on x86_64. There is zero additional benefit to making an x86_64 version. > As well, > I tend to build on one host and install on several (I customize my > distro installer to include my own repository for additional packages), > so eventually avoiding the devel environment would be worth it to me > long-term. You'll end up needing to make RPMs for all the dependencies. The people who have added BitPim to the Gentoo and Debian repositories have done that. > Sometime in the future, I might supply a SPEC file Here is the one used today: http://svn.sourceforge.net/viewcvs.cgi/bitpim/trunk/bitpim/packaging/bitpim.spec?view=markup > that would actually do the entire build, There isn't anything to build, unless you want to fold all the dependencies into a single "binary" package. > temporarily stuck with this error and don't know which package I need > installed. Go back to the developer page. Look at the wxPython section. Note the text in bold. Roger |