Alle martedì 20 marzo 2012, Ritesh Raj Sarraf ha scritto:
> On Tuesday 20 March 2012 08:05 PM, Pino Toscano wrote:
> > shlibs, postrm and postinst in your case are created by
> > dh_makeshlibs; it could be there's a (private?) shared library
> > with a wrong/missing SONAME.
> > Can you please point to the appmenu-qt source and to your
> > packaging? Can you please provide the full list of files installed
> > in the package?
>
> Thanks Pino.
>
> Yes, there is a private library shipped.
Ok, now it is a bit more clear.
cmake library targets, even if with type MODULE, get a SONAME.
dh_makeshlibs scans for .so files with SONAME, and given libappmenu-
qt.so has a file name with a dash (like "foo-bar.so"), dh_makeshlibs
thinks "qt" is the SONAME, hence filling shlibs and running ldconfig in
post{inst,rm}.
The easiest way to avoid that is not running dh_makeshlibs at all (since
the source builds only a plugin at the moment), or exclude the plugin
directory like this:
| override_dh_makeshlibs:
| dh_makeshlibs -Xqt4/plugins
(not usr/lib/... so it won't break the day qt4 becomes multi-arch)
Ah, a couple of minor notes on packaging:
- B-D libqt4-dev (>= 4.8) -- needs the epoch in the qt4 version
(e.g. 4:4.8), otherwise even, say, qt4 4:4.1 is a valid version...
- B-D kde-workspace-dev -- can be switched to kde-workspace-dev, now
- short and long descriptions: use "Qt" instead of "qt" and "QT"
--
Pino Toscano
Attachment:
signature.asc
Description: This is a digitally signed message part.