Jérémy, > Your package won't install on some systems anyway, since libv8 does not > build/run on all architectures.
I don't need it to install on all systems. Just the ones I support which are the same as for libv8. >>From what you say it looks like your package dependency on libv8 is > optional ? If that's the case then use a Recommends or Suggests > relationship in debian/control. I don't think I explained my problem or the solution well enough. What I would like to have is a virtual package named 'libv8' which depends on the latest 'libv8-#.#.#', whatever that maybe. This way my package only needs to depend on 'libv8' and not have to guess the version that might be installed on the user's system. Also you could then install libv8 like this: sudo apt-get install libv8 Right now you have to first search for the latest version. The problem stems from the fact that libv8 includes the library version in the library name not just in the package name. I know this has become common (boost does too) but it's a PITA for packages which depend on such packages. Thanks, Joseph -- Cauldron Development LLC http://www.cauldrondevelopment.com/ Cell: 208-409-9128 _______________________________________________ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
