Edgar <[EMAIL PROTECTED]> writes:
> On Tuesday 13 July 2004 21:25, Magnus Therning wrote:
>> Wouldn't the -rpath flag for the linker be the thing to use for this
>> purpose?
>
> Doesn't lintian complain if you use -rpath? Or is that only under certain
> circumstances?
>
> Edgar.
Lintian should o
Rene Engelhard <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Ali Bombali wrote:
> > The right way to do this is to use the X-Debbugs-CC header. Add a line like
> > this to your message's mail header (not to the pseudo header with the
> > package field):
> >
> > X-Debbugs-CC: [EMAIL PROTECTED]
> >
> >
Milan Zamazal <[EMAIL PROTECTED]> writes:
> My package contains binaries using a common shared library, which is not
> intended to be used by other programs. This is a regular shared
> library, not a plugin or other object to be explicitly loaded by the
> binaries, the binaries just normally link
On Tuesday 13 July 2004 21:25, Magnus Therning wrote:
> Wouldn't the -rpath flag for the linker be the thing to use for this
> purpose?
Doesn't lintian complain if you use -rpath? Or is that only under certain
circumstances?
Edgar.
Hi,
I've uploaded some packages to my apt repository on my homepage[1]. Some
are marked with " SPONSOR WANTED ", because - as you may guess -
these packages are looking for a sponsor ;)
* bf = a simple Brainfuck interpreter (with some nice options)
* cpuspeedy = Python script to set CPU
Edgar <[EMAIL PROTECTED]> writes:
> On Tuesday 13 July 2004 21:25, Magnus Therning wrote:
>> Wouldn't the -rpath flag for the linker be the thing to use for this
>> purpose?
>
> Doesn't lintian complain if you use -rpath? Or is that only under certain
> circumstances?
>
> Edgar.
Lintian should o
Rene Engelhard <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Ali Bombali wrote:
> > The right way to do this is to use the X-Debbugs-CC header. Add a line like
> > this to your message's mail header (not to the pseudo header with the
> > package field):
> >
> > X-Debbugs-CC: [EMAIL PROTECTED]
> >
> >
Milan Zamazal <[EMAIL PROTECTED]> writes:
> My package contains binaries using a common shared library, which is not
> intended to be used by other programs. This is a regular shared
> library, not a plugin or other object to be explicitly loaded by the
> binaries, the binaries just normally link
On Tue, Jul 13, 2004 at 11:15:45AM +0200, Milan Zamazal wrote:
>My package contains binaries using a common shared library, which is
>not intended to be used by other programs. This is a regular shared
>library, not a plugin or other object to be explicitly loaded by the
>binaries, the binaries ju
On Tuesday 13 July 2004 21:25, Magnus Therning wrote:
> Wouldn't the -rpath flag for the linker be the thing to use for this
> purpose?
Doesn't lintian complain if you use -rpath? Or is that only under certain
circumstances?
Edgar.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
Hi,
I've uploaded some packages to my apt repository on my homepage[1]. Some
are marked with " SPONSOR WANTED ", because - as you may guess -
these packages are looking for a sponsor ;)
* bf = a simple Brainfuck interpreter (with some nice options)
* cpuspeedy = Python script to set CPU
On Tue, Jul 13, 2004 at 11:15:45AM +0200, Milan Zamazal wrote:
>My package contains binaries using a common shared library, which is
>not intended to be used by other programs. This is a regular shared
>library, not a plugin or other object to be explicitly loaded by the
>binaries, the binaries ju
Adrian 'Dagurashibanipal' von Bidder <[EMAIL PROTECTED]> writes:
> And while I'm at it: the behaviour change is not really dangerous, but
> can cause people to get more spam. (Background: postgrey changed from
> --lookup-by-host to --lookup-by-subnet in Version 1.14) So, is a
> debconf notice e
Adrian 'Dagurashibanipal' von Bidder <[EMAIL PROTECTED]> writes:
> And while I'm at it: the behaviour change is not really dangerous, but
> can cause people to get more spam. (Background: postgrey changed from
> --lookup-by-host to --lookup-by-subnet in Version 1.14) So, is a
> debconf notice e
On Tue, 13 Jul 2004, Milan Zamazal wrote:
> My package contains binaries using a common shared library, which is not
> intended to be used by other programs. This is a regular shared
> library, not a plugin or other object to be explicitly loaded by the
> binaries, the binaries just normally link
On Tuesday 13 July 2004 12.24, martin f krafft wrote:
> also sprach martin f krafft <[EMAIL PROTECTED]> [2004.07.13.1217
+0200]:
> > case "$2" in
> > 0.13*) [...]
> After looking over debconf-devel(7), this should be in the
> postgrey.config script and use db_input rather than db_get. B
On 2004-07-13 Adrian 'Dagurashibanipal' von Bidder <[EMAIL PROTECTED]> wrote:
> [Madduck cc:ed as he is my sponsor - but he tells me he's certainly not
> a debconf expert]
> How do I display a debconf note only on upgrades from versions older
> than x to x or newer? No need to annoy all users...
> "AvB" == Adrian von Bidder <[EMAIL PROTECTED]> writes:
AvB> Call the binaries from a wrapper script that sets up
AvB> LD_LIBRARY_PATH?
This is extra-ugly and I'm not going to do this.
AvB> Not elegant, but isn't it what most Java applications do with
AvB> their environment
also sprach martin f krafft <[EMAIL PROTECTED]> [2004.07.13.1217 +0200]:
> AFAICT, the display of a 'note' is triggered by db_get in postinst.
> Since postinst gets the previous version as arguments to an
> upgrade/configure action, it's a simple case/if statement.
>
> case "$1" in
> configure)
also sprach Adrian 'Dagurashibanipal' von Bidder <[EMAIL PROTECTED]>
[2004.07.13.1204 +0200]:
> How do I display a debconf note only on upgrades from versions
> older than x to x or newer? No need to annoy all users...
AFAICT, the display of a 'note' is triggered by db_get in postinst.
Since post
Hi,
[Madduck cc:ed as he is my sponsor - but he tells me he's certainly not
a debconf expert]
How do I display a debconf note only on upgrades from versions older
than x to x or newer? No need to annoy all users...
(Of course, pointers to examples welcome.)
And while I'm at it: the behaviour
On Tuesday 13 July 2004 11.15, Milan Zamazal wrote:
> How to ensure properly that the binaries can find the
> library?
Call the binaries from a wrapper script that sets up LD_LIBRARY_PATH?
Not elegant, but isn't it what most Java applications do with their
environment variables?
greetings
-- vb
On Sun, Jul 11, 2004 at 09:51:38PM +0200, Pascal Greliche wrote:
>Hi,
>
>I build some packages and I'd like to know my mistakes and how to
>improve them or others.
>The packages I made may be useful for others.
>The first package I'd like to upload is qmail-scanner.
>First from http://qmail-scanne
My package contains binaries using a common shared library, which is not
intended to be used by other programs. This is a regular shared
library, not a plugin or other object to be explicitly loaded by the
binaries, the binaries just normally link to it.
Debian Policy says:
Shared object fi
On Tue, 13 Jul 2004, Milan Zamazal wrote:
> My package contains binaries using a common shared library, which is not
> intended to be used by other programs. This is a regular shared
> library, not a plugin or other object to be explicitly loaded by the
> binaries, the binaries just normally link
On Tuesday 13 July 2004 12.24, martin f krafft wrote:
> also sprach martin f krafft <[EMAIL PROTECTED]> [2004.07.13.1217
+0200]:
> > case "$2" in
> > 0.13*) [...]
> After looking over debconf-devel(7), this should be in the
> postgrey.config script and use db_input rather than db_get. B
On 2004-07-13 Adrian 'Dagurashibanipal' von Bidder <[EMAIL PROTECTED]> wrote:
> [Madduck cc:ed as he is my sponsor - but he tells me he's certainly not
> a debconf expert]
> How do I display a debconf note only on upgrades from versions older
> than x to x or newer? No need to annoy all users...
> "AvB" == Adrian von Bidder <[EMAIL PROTECTED]> writes:
AvB> Call the binaries from a wrapper script that sets up
AvB> LD_LIBRARY_PATH?
This is extra-ugly and I'm not going to do this.
AvB> Not elegant, but isn't it what most Java applications do with
AvB> their environment
also sprach martin f krafft <[EMAIL PROTECTED]> [2004.07.13.1217 +0200]:
> AFAICT, the display of a 'note' is triggered by db_get in postinst.
> Since postinst gets the previous version as arguments to an
> upgrade/configure action, it's a simple case/if statement.
>
> case "$1" in
> configure)
also sprach Adrian 'Dagurashibanipal' von Bidder <[EMAIL PROTECTED]> [2004.07.13.1204
+0200]:
> How do I display a debconf note only on upgrades from versions
> older than x to x or newer? No need to annoy all users...
AFAICT, the display of a 'note' is triggered by db_get in postinst.
Since post
Hi,
[Madduck cc:ed as he is my sponsor - but he tells me he's certainly not
a debconf expert]
How do I display a debconf note only on upgrades from versions older
than x to x or newer? No need to annoy all users...
(Of course, pointers to examples welcome.)
And while I'm at it: the behaviour
On Tuesday 13 July 2004 11.15, Milan Zamazal wrote:
> How to ensure properly that the binaries can find the
> library?
Call the binaries from a wrapper script that sets up LD_LIBRARY_PATH?
Not elegant, but isn't it what most Java applications do with their
environment variables?
greetings
-- vb
On Sun, Jul 11, 2004 at 09:51:38PM +0200, Pascal Greliche wrote:
>Hi,
>
>I build some packages and I'd like to know my mistakes and how to
>improve them or others.
>The packages I made may be useful for others.
>The first package I'd like to upload is qmail-scanner.
>First from http://qmail-scanne
My package contains binaries using a common shared library, which is not
intended to be used by other programs. This is a regular shared
library, not a plugin or other object to be explicitly loaded by the
binaries, the binaries just normally link to it.
Debian Policy says:
Shared object fi
34 matches
Mail list logo