Hi!
On Thu, 2024-11-28 at 09:30:15 -0300, Santiago Ruano Rincón wrote:
> This is what grep does [0]:
>
> #!/bin/sh
> set -e
>
> export DEB_BUILD_PROFILES="nocheck nodoc" DEB_BUILD_OPTIONS="nocheck
> nodoc"
>
> dpkg-source --before-build `pwd`
Nit: I'd probably use «$(pwd)» her
Hi!
[ Perhaps you already managed to solve this, but just in case. :) ]
On Thu, 2024-11-28 at 12:43:05 +0100, Santiago Vila wrote:
> Many GNU packages have built-in tests that test the just-built programs.
>
> Is there a general procedure/trick/idiom to modify them so that they test
> the instal
Hi Santiago,
Am Thu, Nov 28, 2024 at 09:30:15AM -0300 schrieb Santiago Ruano Rincón:
> > Many GNU packages have built-in tests that test the just-built programs.
This reminds me to my attempt to write some autopkgtest for tar. I've
created an according bug report[1] (in CC) but I did not went re
On Thu, 28 Nov 2024 12:43:05 +0100
Santiago Vila wrote:
> Dear mentors:
>
> Many GNU packages have built-in tests that test the just-built
> programs.
>
> Is there a general procedure/trick/idiom to modify them so that
> they test the installed version instead? (so that they can be
> reused wit
Hey tocayo,
El 28/11/24 a las 12:43, Santiago Vila escribió:
> Dear mentors:
>
> Many GNU packages have built-in tests that test the just-built programs.
>
> Is there a general procedure/trick/idiom to modify them so that they test
> the installed version instead? (so that they can be reused wit
Dear mentors:
Many GNU packages have built-in tests that test the just-built programs.
Is there a general procedure/trick/idiom to modify them so that they test
the installed version instead? (so that they can be reused with minimal
changes).
(I'd like to do this for several packages without re
6 matches
Mail list logo
