On 29-Sep-2000 Yves Arrouye wrote:
> I am sure it's an FAQ, sorry... I am making a package with a library package
> and a development package. I started with debhelper. My debian/postinst and
> debian/postrm call ldconfig. Now what happens is that they end up in my
> libxxx-dev package, not my lib
I am sure it's an FAQ, sorry... I am making a package with a library package
and a development package. I started with debhelper. My debian/postinst and
debian/postrm call ldconfig. Now what happens is that they end up in my
libxxx-dev package, not my libxxx1 one (which is populated using
dh_movefi
On 29-Sep-2000 Yves Arrouye wrote:
> I am sure it's an FAQ, sorry... I am making a package with a library package
> and a development package. I started with debhelper. My debian/postinst and
> debian/postrm call ldconfig. Now what happens is that they end up in my
> libxxx-dev package, not my li
I am sure it's an FAQ, sorry... I am making a package with a library package
and a development package. I started with debhelper. My debian/postinst and
debian/postrm call ldconfig. Now what happens is that they end up in my
libxxx-dev package, not my libxxx1 one (which is populated using
dh_movef
On Thu, Sep 28, 2000 at 10:33:25PM +0200, Stefan Alfredsson wrote:
> 1. Developer lives on the edge and usually has the latest libs installed
> 2. Package becomes dependant upon bleedingedge version of libs
>-- BUT it is not really needed, for example gtk1.2.1 might
>do just aswell as gtk1.
On Thu, Sep 28, 2000 at 10:33:25PM +0200, Stefan Alfredsson wrote:
> 1. Developer lives on the edge and usually has the latest libs installed
> 2. Package becomes dependant upon bleedingedge version of libs
>-- BUT it is not really needed, for example gtk1.2.1 might
>do just aswell as gtk1
6 matches
Mail list logo
