Re: getconf(1) interface considered cross-harmful
On Thu, 2017-10-19 at 10:51:30 +0100, Simon McVittie wrote:
> On Thu, 19 Oct 2017 at 10:50:36 +0200, Guillem Jover wrote:
> > When it comes to LFS, starting with dpkg 1.19.0 you can now use the
> > new «lfs» feature from the «future» feature area
>
> ... or if your upstream uses Autotools, ask them to add AC_SYS_LARGEFILE
> to configure.ac, which as far as I can tell does the right thing.
Sure, and that was already covered in the lintian tag as one of the
possible solutions. My assumption for adding that new build flag
feature has been that if maintainers are currently using getconf(1)
it is because either the package does not use autoconf, or they might
be uncomfortable patching it or similar. And this would give an easy
migration path.
I filed #879935, and the lintian tag clarification got applied, the
remaining part is for emitting a tag on wrong getconf(1) usage.
Thanks,
Guillem
Reply to: