On Sun, Feb 09, 2014 at 03:10:26PM +0000, Sune Vuorela wrote: > On 2014-02-08, Roelof Wobben <rwob...@hotmail.com> wrote: > > DEB_DH_MAKESHLIBS_ARGS_libcjs0c = -Xusr/lib/cjs-1.0/ -V'libcjs0c (>= > > $(DEB_UPSTREAM_VERSION)), libcjs0-$(LIBMOZJS)' -- -c4 > In this case, it ensures that anything that links libcjs0c ensures that > it is installed along with the libcjs0-$(LIBMOZJS) package. That's the problem, it doesn't.
It ensures that any *Debian package* built this way will pull it in. shlibs are only looked at at Debian package build time and is used to assist in the generation of the Depends: line for that package being built. Assuming this LIBMOZJS thing is required for libcjs0 to work, then any program compiled against libcjs0 that isn't a Debian package has the potential to break. If libcjs0 needs that LIBMOZJS package to work, then it should be a dependency of libcjs0. It should not be some kludge using shlibs. - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140209213711.gc13...@enc.com.au
