On Sun, 2005-11-13 at 20:28 +0000, Chris Cannam wrote: > Does that mean that most packagers feel that some failed dependencies > are OK?
Yes. For instance, bundling GTK+ or Pango would be quite unusual. > Does autopackage normally warn and exit if a vital library not > bundled is not found? It does, assuming you put a dependency check in. It can also resolve some dependencies itself. > I would guess that if ~/.config/menus/[something other than debian-*] > exists, it's probably a bad idea to run update-menus. I'd much rather > not have my new package on the K menu than have everything else go > missing. OK. I'll add this to the todo list. > > [...] the new support in 1.2 can transparently fix it for > > every C++ app. > > How? The brute force approach. Each binary is compiled twice, once with each compiler. A binary delta is taken between the two to reduce package size. LZMA compression is used to shrink the package still further. So, it increases package compile time a lot, and package size a little bit, but it's guaranteed to work. We looked at more elegant or efficient solutions, but they were usually foiled by GCC bugs. thanks -mike ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
