Re: place of ldconfig in postinst
On Fri, Nov 02, 2001 at 10:17:36AM -0800, Sean 'Shaleh' Perry wrote: This is no different from working with a bunch of coders and everyone agreeing on a common code formatting. Talk to the maintainer of debhelper ? dh_make is NOT maintained by Joey Hess, the debhelper maint. In fact he has nothing to do with it. Oh, sorry. I was confused by the fact that the maintainer's scripts were kept under /usr/share/debhelper. Should we ask Craig Small [EMAIL PROTECTED] to sync those .ex files with Lintian ? -- Eric VAN BUGGENHAUT [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: place of ldconfig in postinst
Should we ask Craig Small [EMAIL PROTECTED] to sync those .ex files with Lintian ? actually he should sync them with debhelper. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: place of ldconfig in postinst
On Fri, Nov 02, 2001 at 10:17:36AM -0800, Sean 'Shaleh' Perry wrote: This is no different from working with a bunch of coders and everyone agreeing on a common code formatting. Talk to the maintainer of debhelper ? dh_make is NOT maintained by Joey Hess, the debhelper maint. In fact he has nothing to do with it. Oh, sorry. I was confused by the fact that the maintainer's scripts were kept under /usr/share/debhelper. Should we ask Craig Small [EMAIL PROTECTED] to sync those .ex files with Lintian ? -- Eric VAN BUGGENHAUT [EMAIL PROTECTED]
Re: place of ldconfig in postinst
Should we ask Craig Small [EMAIL PROTECTED] to sync those .ex files with Lintian ? actually he should sync them with debhelper.
Re: place of ldconfig in postinst
On Thu, Nov 01, 2001 at 10:56:25AM -0500, Steve M. Robbins wrote: On Thu, Nov 01, 2001 at 04:00:34PM +0100, Eric Van Buggenhaut wrote: Hi, I'm building my first packages with shared library. This is what my postinst states: case $1 in configure) ldconfig ;; abort-upgrade|abort-remove|abort-deconfigure) ;; *) echo postinst called with unknown argument \`$1' 2 By the way, if you use the debhelper scripts (dh_makeshlibs in particular) , you don't need to write the postinst by hand, and as a bonus, lintian will not complain about it. OK, done ! -- Eric VAN BUGGENHAUT [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: place of ldconfig in postinst
This is no different from working with a bunch of coders and everyone agreeing on a common code formatting. Talk to the maintainer of debhelper ? dh_make is NOT maintained by Joey Hess, the debhelper maint. In fact he has nothing to do with it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: place of ldconfig in postinst
On Fri, Nov 02, 2001 at 10:17:36AM -0800, Sean 'Shaleh' Perry wrote: Talk to the maintainer of debhelper ? dh_make is NOT maintained by Joey Hess, the debhelper maint. In fact he has nothing to do with it. Write to [EMAIL PROTECTED] or file a bug against it. -- Christian Surchi | [EMAIL PROTECTED] | [EMAIL PROTECTED] FLUG: http://www.firenze.linux.it | Debian GNU/Linux: http://www.debian.org Consider a spherical bear, in simple harmonic motion... -- Professor in the UCB physics department -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: place of ldconfig in postinst
On Thu, Nov 01, 2001 at 08:18:20PM -0800, Sean 'Shaleh' Perry wrote: On 01-Nov-2001 Eric Van Buggenhaut wrote: Hi, I'm building my first packages with shared library. This is what my postinst states: Lintian is a collection of stupid shell scripts. It tries to catch thr common cases and does a pretty good job. My best suggestion is to write your code in the style of most of the other scripts and everyone is happy. This isn't 'my' code, it's an almost exact copy of /usr/share/debhelper/dh_make/debian/postinst.ex So I'd expect it to be 'in the style of most of the other scripts'. This is no different from working with a bunch of coders and everyone agreeing on a common code formatting. Talk to the maintainer of debhelper ? -- Eric VAN BUGGENHAUT [EMAIL PROTECTED]
Re: place of ldconfig in postinst
On Thu, Nov 01, 2001 at 10:56:25AM -0500, Steve M. Robbins wrote: On Thu, Nov 01, 2001 at 04:00:34PM +0100, Eric Van Buggenhaut wrote: Hi, I'm building my first packages with shared library. This is what my postinst states: case $1 in configure) ldconfig ;; abort-upgrade|abort-remove|abort-deconfigure) ;; *) echo postinst called with unknown argument \`$1' 2 By the way, if you use the debhelper scripts (dh_makeshlibs in particular) , you don't need to write the postinst by hand, and as a bonus, lintian will not complain about it. OK, done ! -- Eric VAN BUGGENHAUT [EMAIL PROTECTED]
Re: place of ldconfig in postinst
This is no different from working with a bunch of coders and everyone agreeing on a common code formatting. Talk to the maintainer of debhelper ? dh_make is NOT maintained by Joey Hess, the debhelper maint. In fact he has nothing to do with it.
Re: place of ldconfig in postinst
On Fri, Nov 02, 2001 at 10:17:36AM -0800, Sean 'Shaleh' Perry wrote: Talk to the maintainer of debhelper ? dh_make is NOT maintained by Joey Hess, the debhelper maint. In fact he has nothing to do with it. Write to [EMAIL PROTECTED] or file a bug against it. -- Christian Surchi | [EMAIL PROTECTED] | [EMAIL PROTECTED] FLUG: http://www.firenze.linux.it | Debian GNU/Linux: http://www.debian.org Consider a spherical bear, in simple harmonic motion... -- Professor in the UCB physics department
Re: place of ldconfig in postinst
case $1 in configure) ldconfig W: iiwusynth: postinst-unsafe-ldconfig Sorry, I don't get it ! Lintian is cannot parse shell scripts, it checks for some common variants, and warns if your version didn't match what it expected. Since you do the right thing, just ignore this warning, as it's a false alarm. PGP signature
Re: place of ldconfig in postinst
On Thu, Nov 01, 2001 at 04:13:36PM +0100, Gergely Nagy wrote: case $1 in configure) ldconfig W: iiwusynth: postinst-unsafe-ldconfig Sorry, I don't get it ! Lintian is cannot parse shell scripts, it checks for some common variants, and warns if your version didn't match what it expected. Since you do the right thing, just ignore this warning, as it's a false alarm. maybe he waits for and if construct. -- Christian Surchi | [EMAIL PROTECTED] | [EMAIL PROTECTED] FLUG: http://www.firenze.linux.it | Debian GNU/Linux: http://www.debian.org The geeks shall inherit the earth. -- Karl Lehenbauer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: place of ldconfig in postinst
On Thu, Nov 01, 2001 at 04:18:46PM +0100, Christian Surchi wrote: On Thu, Nov 01, 2001 at 04:13:36PM +0100, Gergely Nagy wrote: case $1 in configure) ldconfig W: iiwusynth: postinst-unsafe-ldconfig Sorry, I don't get it ! Lintian is cannot parse shell scripts, it checks for some common variants, and warns if your version didn't match what it expected. Since you do the right thing, just ignore this warning, as it's a false alarm. maybe he waits for and if construct. The lintian check is looking for an if construct. You can see the precise check in /usr/share/lintian/checks/shared-libs. -Steve P.S. You guys should pay more attention to debian-mentors: the answer was contained in a post made not more than 2-3 days ago! -- by Rocket to the Moon, by Airplane to the Rocket, by Taxi to the Airport, by Frontdoor to the Taxi, by throwing back the blanket and laying down the legs ... - They Might Be Giants -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: place of ldconfig in postinst
On Thu, Nov 01, 2001 at 04:00:34PM +0100, Eric Van Buggenhaut wrote: Hi, I'm building my first packages with shared library. This is what my postinst states: case $1 in configure) ldconfig ;; abort-upgrade|abort-remove|abort-deconfigure) ;; *) echo postinst called with unknown argument \`$1' 2 By the way, if you use the debhelper scripts (dh_makeshlibs in particular) , you don't need to write the postinst by hand, and as a bonus, lintian will not complain about it. -S -- by Rocket to the Moon, by Airplane to the Rocket, by Taxi to the Airport, by Frontdoor to the Taxi, by throwing back the blanket and laying down the legs ... - They Might Be Giants -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: place of ldconfig in postinst
On 01-Nov-2001 Eric Van Buggenhaut wrote: Hi, I'm building my first packages with shared library. This is what my postinst states: Lintian is a collection of stupid shell scripts. It tries to catch thr common cases and does a pretty good job. My best suggestion is to write your code in the style of most of the other scripts and everyone is happy. This is no different from working with a bunch of coders and everyone agreeing on a common code formatting. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: place of ldconfig in postinst
On Thu, Nov 01, 2001 at 04:00:34PM +0100, Eric Van Buggenhaut wrote: Hi, I'm building my first packages with shared library. This is what my postinst states: case $1 in configure) ldconfig ;; abort-upgrade|abort-remove|abort-deconfigure) ;; *) echo postinst called with unknown argument \`$1' 2 By the way, if you use the debhelper scripts (dh_makeshlibs in particular) , you don't need to write the postinst by hand, and as a bonus, lintian will not complain about it. -S -- by Rocket to the Moon, by Airplane to the Rocket, by Taxi to the Airport, by Frontdoor to the Taxi, by throwing back the blanket and laying down the legs ... - They Might Be Giants
Re: place of ldconfig in postinst
On Thu, Nov 01, 2001 at 04:18:46PM +0100, Christian Surchi wrote: On Thu, Nov 01, 2001 at 04:13:36PM +0100, Gergely Nagy wrote: case $1 in configure) ldconfig W: iiwusynth: postinst-unsafe-ldconfig Sorry, I don't get it ! Lintian is cannot parse shell scripts, it checks for some common variants, and warns if your version didn't match what it expected. Since you do the right thing, just ignore this warning, as it's a false alarm. maybe he waits for and if construct. The lintian check is looking for an if construct. You can see the precise check in /usr/share/lintian/checks/shared-libs. -Steve P.S. You guys should pay more attention to debian-mentors: the answer was contained in a post made not more than 2-3 days ago! -- by Rocket to the Moon, by Airplane to the Rocket, by Taxi to the Airport, by Frontdoor to the Taxi, by throwing back the blanket and laying down the legs ... - They Might Be Giants
Re: place of ldconfig in postinst
case $1 in configure) ldconfig W: iiwusynth: postinst-unsafe-ldconfig Sorry, I don't get it ! Lintian is cannot parse shell scripts, it checks for some common variants, and warns if your version didn't match what it expected. Since you do the right thing, just ignore this warning, as it's a false alarm. pgpwtBxA0PQ8u.pgp Description: PGP signature
Re: place of ldconfig in postinst
On Thu, Nov 01, 2001 at 04:13:36PM +0100, Gergely Nagy wrote: case $1 in configure) ldconfig W: iiwusynth: postinst-unsafe-ldconfig Sorry, I don't get it ! Lintian is cannot parse shell scripts, it checks for some common variants, and warns if your version didn't match what it expected. Since you do the right thing, just ignore this warning, as it's a false alarm. maybe he waits for and if construct. -- Christian Surchi | [EMAIL PROTECTED] | [EMAIL PROTECTED] FLUG: http://www.firenze.linux.it | Debian GNU/Linux: http://www.debian.org The geeks shall inherit the earth. -- Karl Lehenbauer
Re: place of ldconfig in postinst
On 01-Nov-2001 Eric Van Buggenhaut wrote: Hi, I'm building my first packages with shared library. This is what my postinst states: Lintian is a collection of stupid shell scripts. It tries to catch thr common cases and does a pretty good job. My best suggestion is to write your code in the style of most of the other scripts and everyone is happy. This is no different from working with a bunch of coders and everyone agreeing on a common code formatting.
