Arch Linux

I regard this as a feature, not a bug.

Try running makepkg --printsrcinfo, you'll see things like

pkgver = perl>=

The new linting checks for invalid dependency specifiers quite rightly dislike this, but they don't know how to run this complicated if statement, for the same reason as  FS#55004 

IMHO the versioned dependency should be dropped. Perl uses versioned libdirs now, anyway.

r8168 is affected too, it uses versioned kernel depends.

The simplest solution is probably to use something like

depends+=("perl${_perlver_min:+>=$_perlver_min}" "perl${_perlver_max:+<$_perlver_max}")

That seems to be just hiding the issue.

Well, or inline it, depending on how large the cmdline is. The r8168 PKGBUILD uses:

depends=("linux>=$_kernver" "linux<${_kernver/.*}.$(expr ${_kernver/*.} + 1)")

Which... well, fallback values won't really work there, actually. It would need some global helper function (which will be eval'ed just fine)

perlver() { perl -e '$v = $^V->{version}; print $v->[0].".".($v->[1]+$ARGV[0]);' $1; }

if [[ $(find "$pkgdir/usr/lib/perl5/" -name "*.so") ]]; then
depends+=("perl>=$(perlver)" "perl<$(perlver 1)")
fi

Should work fine, and the .SRCINFO it generates will actually contain the versioned specifier.
(It will also always claim to depend on versioned perl, which I guess is better than never.)

This assumes we don't want to just drop the versioned dependency entirely due to the existing versioned libdir and detect-old-perl-modules.hook which will loudly warn the user on *every* upgrade that modifies /usr/lib/perl5, if any perl modules are the wrong version.

We don't usually try to version our dependencies in the first place, and IIRC we did this by perl because of the infamous "your mismatched modules will crash the perl interpreter even if you don't try using those modules" thing, which is now fixed anyway due to https://www.archlinux.org/news/perl-library-path-change/

I think this is perl package bug because of /usr/share/makepkg-template/perl-binary-module-dependency.template belongs to perl.

I wanted to wait for a final decision from Allan before doing anything here, but apparently people keep running into this. We don't need the template any more so feel free to remove it from affected packages.

> That seems to be just hiding the issue.

Actually, thinking about this, this is more or less the same as libdepends/libprovides, which also evaluate the versioned component (in a much more complex fashion) only in the actual packaging stage but not when generating srcinfo. Whether it *should* be versioned is another question, of course.

And thinking about that, I think if people do want versioned dependencies this is better implemented as a libmakepkg drop-in.

To clarify this bug... The failure is only when using other variables or functions defined within the package() function. If these are defined at a global scope, all is fine.

There's other issues too, when trying to define metadata within package(), like  FS#55004