On Sat, Feb 01, 2003 at 05:00:19PM -0500, Joey Hess wrote:
> The module package may not even be installed, the module may be used
> conditionally, a versioned dependency may be needed, multiple packages
> may provide the same module (and a dependency on a virtual package or an
> ored dependency ne
Steve Kemp wrote:
> Mapping from a perl module to a Debian package should be trivial,
> I would have thought.
>
> Given the system upon which dh_perl would be run would have the
> modules installed it should be a simple matter of running
> 'dpkg --search path/to/pe
ng from a perl module to a Debian package should be trivial,
I would have thought.
Given the system upon which dh_perl would be run would have the
modules installed it should be a simple matter of running
'dpkg --search path/to/perl/module.pm' - or am I missing something
obvi
On Sat, Feb 01, 2003 at 05:00:19PM -0500, Joey Hess wrote:
> The module package may not even be installed, the module may be used
> conditionally, a versioned dependency may be needed, multiple packages
> may provide the same module (and a dependency on a virtual package or an
> ored dependency ne
Steve Kemp wrote:
> Mapping from a perl module to a Debian package should be trivial,
> I would have thought.
>
> Given the system upon which dh_perl would be run would have the
> modules installed it should be a simple matter of running
> 'dpkg --search path/to/pe
ng from a perl module to a Debian package should be trivial,
I would have thought.
Given the system upon which dh_perl would be run would have the
modules installed it should be a simple matter of running
'dpkg --search path/to/perl/module.pm' - or am I missing something
obvi
bution that would easily stretch the
> limits of any tool trying to calculate Perl module dependencies.
>
> As such, I'd rather not see something like this in dh_perl, whose output
> is expected to be used unmodified. It should be in some other tool which
> maintainers can run and
On Sat, Feb 01, 2003 at 12:57:31PM +, Roger Leigh wrote:
> Colin Watson <[EMAIL PROTECTED]> writes:
> > dh_perl doesn't (currently) attempt to calculate general module
> > dependencies, only core dependencies.
>
> OK, thanks.
>
> I guess that, due to
bution that would easily stretch the
> limits of any tool trying to calculate Perl module dependencies.
>
> As such, I'd rather not see something like this in dh_perl, whose output
> is expected to be used unmodified. It should be in some other tool which
> maintainers can run and
Colin Watson <[EMAIL PROTECTED]> writes:
> On Fri, Jan 31, 2003 at 10:15:31PM +, Roger Leigh wrote:
> > I'm using dh_perl to calculate the package dependencies for a perl
> > script in the cupsys-driver-gimpprint package. I thought this was
> > working, but i
On Sat, Feb 01, 2003 at 12:57:31PM +, Roger Leigh wrote:
> Colin Watson <[EMAIL PROTECTED]> writes:
> > dh_perl doesn't (currently) attempt to calculate general module
> > dependencies, only core dependencies.
>
> OK, thanks.
>
> I guess that, due to
Colin Watson <[EMAIL PROTECTED]> writes:
> On Fri, Jan 31, 2003 at 10:15:31PM +, Roger Leigh wrote:
> > I'm using dh_perl to calculate the package dependencies for a perl
> > script in the cupsys-driver-gimpprint package. I thought this was
> > working, but i
On Fri, Jan 31, 2003 at 10:15:31PM +, Roger Leigh wrote:
> I'm using dh_perl to calculate the package dependencies for a perl
> script in the cupsys-driver-gimpprint package. I thought this was
> working, but it's not getting the dependencies right.
dh_perl doesn'
I'm using dh_perl to calculate the package dependencies for a perl
script in the cupsys-driver-gimpprint package. I thought this was
working, but it's not getting the dependencies right.
In debian/rules, I use "dh_perl -a" in the binary-arch target.
$ cat
On Fri, Jan 31, 2003 at 10:15:31PM +, Roger Leigh wrote:
> I'm using dh_perl to calculate the package dependencies for a perl
> script in the cupsys-driver-gimpprint package. I thought this was
> working, but it's not getting the dependencies right.
dh_perl doesn'
I'm using dh_perl to calculate the package dependencies for a perl
script in the cupsys-driver-gimpprint package. I thought this was
working, but it's not getting the dependencies right.
In debian/rules, I use "dh_perl -a" in the binary-arch target.
$ cat
On Thu, Jan 10, 2002 at 08:24:52PM +0100, Alex Berger wrote:
> hi list,
>
> does dh_perl only check for any dependecies on the package 'perl' or also
> for any perl modules which are used in the scripts, eg. for libwww-perl??
It will find any perl scripts, and add the ap
hi list,
does dh_perl only check for any dependecies on the package 'perl' or also
for any perl modules which are used in the scripts, eg. for libwww-perl??
alex.
--
Alex Berger, registered linux user #138506
mail:[EMAIL PROTECTED] jabber:[EMAIL PROTECTED]
On Thu, Jan 10, 2002 at 08:24:52PM +0100, Alex Berger wrote:
> hi list,
>
> does dh_perl only check for any dependecies on the package 'perl' or also
> for any perl modules which are used in the scripts, eg. for libwww-perl??
It will find any perl scripts, and add the ap
hi list,
does dh_perl only check for any dependecies on the package 'perl' or also
for any perl modules which are used in the scripts, eg. for libwww-perl??
alex.
--
Alex Berger, registered linux user #138506
mail:[EMAIL PROTECTED] jabber:[EMAIL PROTECTED]
--
To UNSUBSCRIBE
20 matches
Mail list logo
