Bug#546199: libsoprano4: soprano-daemon must depend on libsoprano
Hello, On šeštadienis 27 Vasaris 2010 18:30:18 Thomas Koch wrote: > Debian Policy, 3.5: > "For example, a dependency entry must be provided for any shared libraries > required by a dynamically-linked executable binary in a package." > > % dpkg -S /usr/bin/sopranod > soprano-daemon: /usr/bin/sopranod > % ldd /usr/bin/sopranod | grep libsoprano > libsoprano.so.4 => /usr/lib/libsoprano.so.4 > libsopranoserver.so.1 => /usr/lib/libsopranoserver.so.1 > > For me, the policy together with these two commands make it cristal clear > that there is no other posibility then: soprano-daemon MUST depend on > libsoprano4. It's irrelevant which package is useful or not or what any > kind of user may want or know. If I install a binary, then this binary > must depend on all the libraries it needs to run. Which part of "not intended for end user" don't you understand? Probably package description is not explicit about this but I'll try to correct it to satisfy people who enjoy such nitpicking. What's relevant and what's irrelevant are up to package maintainer(s) to decide. So far you have failed to change my opinion. What is more, the fact that you ignore the broad picture does not really help. > I did see, that many applications depend on libsoprano4 and that it's > therefor very unlikely, that anybody would ever install soprano-daemon > without having libsoprano4 already installed. - But this is irrelevant. I > must be possible to install any random package in Debian and have it work > without relying on packages that are not in the dependency tree of this > single package. So far you have not specified what's your real world problem with soprano- daemon (rather than a random package). To be honest, I'm already tired of this thread so let's just end it here. -- Modestas Vainius signature.asc Description: This is a digitally signed message part.
Bug#546199: libsoprano4: soprano-daemon must depend on libsoprano
Hi, > The facts are that: > > 1) libsoprano4 needs soprano-daemon for the library to be useful at > runtime; 2) soprano-daemon is not supposed to be installed or directly > used by users. I guess you are annoyed that soprano-daemon is not removed > when you remove libsoprano4. But that's what apt autoremove is for. > > > However there's the problem with the circular dependency. Since > > soprano-daemon must depend on libsoprano4, you can only delete the > > opposite dependecy, from libsoprano4 to soprano-daemon. > > > > If libsoprano4 also depends on soprano-daemon, then there's no reason to > > build two separate packages in the first place and you merge them into > > one package. > > One of the reasons is debian policy which claims that support binaries for > libraries should be shipped in the packages of their own. > Debian Policy, 3.5: "For example, a dependency entry must be provided for any shared libraries required by a dynamically-linked executable binary in a package." % dpkg -S /usr/bin/sopranod soprano-daemon: /usr/bin/sopranod % ldd /usr/bin/sopranod | grep libsoprano libsoprano.so.4 => /usr/lib/libsoprano.so.4 libsopranoserver.so.1 => /usr/lib/libsopranoserver.so.1 For me, the policy together with these two commands make it cristal clear that there is no other posibility then: soprano-daemon MUST depend on libsoprano4. It's irrelevant which package is useful or not or what any kind of user may want or know. If I install a binary, then this binary must depend on all the libraries it needs to run. I did see, that many applications depend on libsoprano4 and that it's therefor very unlikely, that anybody would ever install soprano-daemon without having libsoprano4 already installed. - But this is irrelevant. I must be possible to install any random package in Debian and have it work without relying on packages that are not in the dependency tree of this single package. Best regards, Thomas Koch, http://www.koch.ro -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201002271730.18702.tho...@koch.ro
Bug#546199: libsoprano4: soprano-daemon must depend on libsoprano
Hello, On šeštadienis 27 Vasaris 2010 14:24:26 Thomas Koch wrote: > Your statement is confusing. You're perfectly right, that soprano-daemon > can not work without libsoprano4. Therefor I asked you, to put libsoprano4 > in the dependency list for soprano-daemon. You do even install binaries to > /usr/bin that depend on libsoprano. I'm saying that it makes no sense to install soprano-daemon if libsoprano4 is not installed (which means there are no apps which *actually* use soprano) on your system. soprano-daemon is merely a support package for libsoprano4. The same logic can be applied to binary and data packages. What is more, soprano is packaged the same way as libc-bin and libc6. The facts are that: 1) libsoprano4 needs soprano-daemon for the library to be useful at runtime; 2) soprano-daemon is not supposed to be installed or directly used by users. I guess you are annoyed that soprano-daemon is not removed when you remove libsoprano4. But that's what apt autoremove is for. > However there's the problem with the circular dependency. Since > soprano-daemon must depend on libsoprano4, you can only delete the > opposite dependecy, from libsoprano4 to soprano-daemon. > > If libsoprano4 also depends on soprano-daemon, then there's no reason to > build two separate packages in the first place and you merge them into one > package. One of the reasons is debian policy which claims that support binaries for libraries should be shipped in the packages of their own. -- Modestas Vainius signature.asc Description: This is a digitally signed message part.
Bug#546199: libsoprano4: soprano-daemon must depend on libsoprano
> On šeštadienis 27 Vasaris 2010 13:32:27 Thomas Koch wrote: > > Hi, > > > > I don't believe, that eliminating the soprano-daemon -> libsoprano4 > > dependency is a solution. ldd shows, that the shared libraries included > > in soprano-daemon depend on libsoprano4. > > You should rather change the dependency from libsoprano4 to > > soprano-daemon into a recommendation. > > Please justify your opinion. On the contrary, I believe soprano-daemon is > useless as a standalone package and libsoprano4 is a lot more important. Your statement is confusing. You're perfectly right, that soprano-daemon can not work without libsoprano4. Therefor I asked you, to put libsoprano4 in the dependency list for soprano-daemon. You do even install binaries to /usr/bin that depend on libsoprano. However there's the problem with the circular dependency. Since soprano-daemon must depend on libsoprano4, you can only delete the opposite dependecy, from libsoprano4 to soprano-daemon. If libsoprano4 also depends on soprano-daemon, then there's no reason to build two separate packages in the first place and you merge them into one package. Best regards, Thomas Koch, http://www.koch.ro -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201002271324.26151.tho...@koch.ro
Bug#546199: libsoprano4: soprano-daemon must depend on libsoprano
Hello, On šeštadienis 27 Vasaris 2010 13:32:27 Thomas Koch wrote: > Hi, > > I don't believe, that eliminating the soprano-daemon -> libsoprano4 > dependency is a solution. ldd shows, that the shared libraries included > in soprano-daemon depend on libsoprano4. > You should rather change the dependency from libsoprano4 to > soprano-daemon into a recommendation. Please justify your opinion. On the contrary, I believe soprano-daemon is useless as a standalone package and libsoprano4 is a lot more important. -- Modestas Vainius signature.asc Description: This is a digitally signed message part.
Bug#546199: libsoprano4: soprano-daemon must depend on libsoprano
Package: libsoprano4 Version: 2.3.1+dfsg.1-1 Severity: normal Hi, I don't believe, that eliminating the soprano-daemon -> libsoprano4 dependency is a solution. ldd shows, that the shared libraries included in soprano-daemon depend on libsoprano4. You should rather change the dependency from libsoprano4 to soprano-daemon into a recommendation. Best regards, Thomas Koch -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100227113227.5385.12021.report...@localhost.localdomain
