Re: Bug #583585 dpkg-maintscript-helper
- To: Gianluca Ciccarelli <firstname.lastname@example.org>
- Subject: Re: Bug #583585 dpkg-maintscript-helper
- From: Raphael Hertzog <email@example.com>
- Date: Tue, 3 Jan 2012 20:54:50 +0100
- Message-id: <20120103195450.GE29763@rivendell.home.ouaza.com>
- In-reply-to: <20120103180718.GA12111@ict23-13.science.unitn.it>
- References: <20111205100524.GA1279@ict23-13.science.unitn.it> <20111205110845.GI2810@rivendell.home.ouaza.com> <20111206201708.GA7331@borges> <20111207070512.GC26636@rivendell.home.ouaza.com> <20111215132403.GA15149@ict23-13.science.unitn.it> <20111215161247.GD13254@rivendell.home.ouaza.com> <20111228155533.GA12521@ict23-13.science.unitn.it> <20111229092637.GA10360@rivendell.home.ouaza.com> <20120103180718.GA12111@ict23-13.science.unitn.it>
On Tue, 03 Jan 2012, Gianluca Ciccarelli wrote:
> >Good idea, what would be even better is to write immediately a
> >(non-regression) test-case to ensure that the code you wrote work as
> >expected and keeps doing it in the future.
> I'm trying to prepare the test case for my modifications to
> dpkg-maintscript-helper, but if I invoke the script with its name in the
> test's maintainer scripts, of course it invokes my system's version,
> which doesn't integrate the changes, and so the operation I want to test
> is not supported (that is, dpkg-maintscript-helper supports <my-op>
> returns with error).
> I thought to make a local "hack" by invoking the modified script in the
> source code. Is there a smarter way to do it?
You can modify the PATH (environment variable) to point first to the directory
with the modified script. But I usually just install the modified version
in the official place (either manually or with a test package).
sudo cp scripts/dpkg-maintscript-helper.sh /usr/bin/dpkg-maintscript-helper
Raphaël Hertzog ◈ Debian Developer
Pre-order a copy of the Debian Administrator's Handbook and help
liberate it: http://debian-handbook.info/liberation/