[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#950689: Please provide a makefile snippet with common variables used during building perl modules

On Tue, 04 Feb 2020 19:36:34 +0100, gregor herrmann wrote:

> > Not sure about the details yet, like where the .mk snippet should go
> > and what else should be included etc. Happy for any suggestions and
> > patches. 
> I might indeed have suggestions for variables and where to find more
> :)

A quick grep session through our pkg-perl packages shows:

PACKAGE = $(shell dh_listpackages)
TMP     = $(CURDIR)/debian/$(PACKAGE)

Not perl specific …

BUILDHOME = $(CURDIR)/debian/build

Not perl specific, and should be obsolete with debhelper compat level

SKIP_TESTS=$(shell cat debian/tests/pkg-perl/smoke-skip)
TEST_FILES = $(filter-out $(SKIP_TESTS), $(wildcard t/*.t))

Not src:perl related but very common for pkg-perl packages.

PERL_CURRENT := $(shell perl -MConfig -e 'print "$$Config{revision}.$$Config{patchlevel}.$$Config{subversion}"')
PERL_NEXT    := $(shell perl -MConfig -e 'print "$$Config{revision}.$$Config{patchlevel}." . ($$Config{subversion} + 1)')

That might be a good candidate (maybe as PERL_VERSION-*).

PERLVER := $(shell perl -MConfig -e 'print $$Config{version}')

ARCHLIB := $(shell perl -MConfig -e 'print $$Config{vendorarch}')
INDEPLIB := $(shell perl -MConfig -e 'print $$Config{vendorlib}')

That's what started the discussion; I guess we might just use the
"real" names, so maybe PERL_CONFIG_VENDORARCH etc.
Maybe it would make sense to just expose all %Config keys?


 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe

Attachment: signature.asc
Description: Digital Signature

Reply to: