On Mon, Jun 18, 2001 at 04:40:46PM +0200, Domenico Andreoli wrote: > > In the past I have solved this problem by invoking dpkg-shlibdeps > > with a LD_LIBRARY_PATH setting that makes it find the libaries in > > the build tree. This way you get a warning that it couldn't find > > what package provides them, but you don't get a bogus dependency. > > I haven't found a cleaner solution. > > > is LD_LIBRARY_PATH solution alternative to shlibs files? and if a libspell > is already installing on the building system? wouldn't i need to put a > !libpspell2 in Build-Depends?
(You mean using Build-Conflicts.) Using LD_LIBRARY_PATH correctly means that the shlibs file from the new package being built will be used, rather than from the one on the system (if any). So you don't need a Build-Conflicts; you just need to get the dh_shlibdeps call correct. (I've sent you a private email on how to do this; basically use the -l option.) Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London Debian GNU/Linux Developer, see http://people.debian.org/~jdg Donate free food to the world's hungry: see http://www.thehungersite.com/