Red Hat Bugzilla – Bug 200696
No Lua Support in Celestia (i.e., for .celx scripts)
Last modified: 2008-03-01 10:01:47 EST
Description of problem: Celestia has not been compiled with support for lua.
Version-Release number of selected component (if applicable): 1.4.1-2.fc5
How reproducible: Always
Steps to Reproduce:
1. Open Celestia
2. Select File->Open Script
3. Be unable to run any .celx scripts
Actual results: Cannot run any .celx scripts
Expected results: See the .celx scripts appear in file browser, be able to
execute them successfully.
Additional info: After applying the two patches attached, and modifying the spec
file appropriately, it works. Please apply the fix, since, .celx files provide
proper scripting, whereas the legacy .cel files are much more limited.
Created attachment 133299 [details]
This attachment is from http://www.archlinux.org/pipermail/tur-users/attachments/20060603/7dea8cd1/celestia-lua51.bin
Created attachment 133300 [details]
This was written with advice from Hank Ramsey.
Without this patch, Celestia segfaults when try to load a .celx file. This was
discussed on the celestia-developers list, with Hank Ramsey.
Created attachment 133301 [details]
The new spec file that applies the patches and adds the --with-lua option to the configure script.
This is the spec file I modified to successfully create the packages at
I also added the developer documentation, as mentioned in the changelog.
We can't mark celestia.cfg as %config as-is. It will need to move to /etc.
Otherwise, I've incorporated everything in 1.4.1-3 (building in devel now, and
I'll build it for FC5 if that goes well).
I had to add a couple of BuildRequires to build in devel, but that's done now.
I'm building for FC-5 now.
I'll leave this open until we figure out what to do about the celestia.cfg
Lua support is build in. Regarding the celestia.cfg configuration file, I think
we should not keep it under /etc as it's not ordinary (per user) configuration
I'm closing this bug, if you think that the configuration file should go
elsewhere, please open a new bug report.