On Fri, Nov 23, 2001 at 02:13:03PM +0100, Christian BAYLE <[EMAIL PROTECTED]> was heard to say: > > Just a note: those packages are really badly done; if someone does > > base a Debian package on them, they'll want to do some serious cleanup > > (the dependencies are screwed up, they dump user binaries in /usr/lib, > > crystalspace is missing a shlibs file, menufiles are messed up...) -- but on > > the other hand, the author seems to have done the hard work of getting > >Crystal to install nicely into a packagable format.
btw, I meant this as a strictly factual statement. > The things you call user binaries are considered by the developpers as > demo software, that's > why I put all this in /usr/lib/crystalspace/bin. Yes, but Debian policy requires that binaries the user would want to run go in /usr/bin or /usr/games (probably /usr/games in this case) eg, allegro-demo does this. > The shared libs files are specifics to crystalspace loaders, so I did > the same that I found in > apache package, and put this in /usr/lib/crystalspace/lib Hmm, the problem was that programs linked against the crystalspace library don't get a dependency on crystalspace. If you're linking statically but using dynamic modules, you need to add dependencies manually; right now I can install crystalspace-demos without crystalspace, and everything will break. The menu files should also use ?(crystalspace-demos) instead of ?(crystalspace), I think. > The way that is used by developers tu use the libs is to set CRYSTAL var > to /usr/lib/crystalspace/ > And then every things allow then to use the lib Ugh. Daniel -- /-------------------- Daniel Burrows <[EMAIL PROTECTED]> -------------------\ | "Note that fires are not restricted to dormitories. | | Indeed, fire can occur in off-campus residences as well." | | -- Brown University Fire Safety Guide | \---------------------- A duck! -- http://www.python.org ---------------------/