Modestas Vainius <[email protected]> writes:
>> SUGGESTION
>>
>> Please add support for file
>>
c>> debian/dh_norun
>>
>> The file would list those commands that do not need to be run for the
>> current package. Commands would be listed one at a line. Comments
>> would be allowed with "#".
>
> IMHO, this would be very confusing. If you want this, do not use dh sequencer
> at all and list all commands you need in debian/rules (conventional packaging
> method). If your suggestion is implemented, somebody else looking at the
> package will have hard time figuring out what commands will actually be run.
The commands that are rub by dh are displayed to the stdout. The
commands that would be left out would simply not appear in that listing.
This would concentrate on what is actually being run and used in the
package. It is in fact confusing to see run of "dh_perl" if that is
no-op for the package.
The idea of debhelper is to use debian/<file> to control behavior (Cf.
debian/docs, debian/dirs ...)
> If you want to skip only a few commands, use .PHONY overrides, e.g. only this
> line is enough:
>
> PHONY: override_dh_auto_test
For single command yes, but as in my example, there are tens of commands
that need not to be run.
> If you want to skip a bunch of sequential commands, you may also use --before
> / --until / --after.
That's good for finer tuning, but a simple debian/dh_norun file would
just announce "these commands are not used by this package; they have no
relevance"
>> This would speed up packaging in low end machines.
>
> If debhelper program has nothing to do, it will exit fast. Slow down should be
> minimal.
The cost of startup of dh_* is an issue because they are Perl program.
I'm sorry to tell you, but there are PII and PIII CPUs still (I have
those) that I use for testing and the speed is an issue when iterating
over package.
>> Of those, for simple package, sometimes only these are needed (target:
>> binary-arch):
>>
>> dh_testdir
>> dh_testroot
>> dh_installchangelogs
>> dh_installdocs
>> dh_installexamples
>> dh_link
>> dh_strip
>> dh_compress
>> dh_fixperms
>> dh_installdeb
>> dh_shlibdeps
>> dh_gencontrol
>> dh_md5sums
>> dh_builddeb
>
> This is exactly what conventional packaging with debhelper is for. Since you
> want full control over sequence, use this method.
Not full control. There is no need to write full blown debian/rules when
it could simply read:
# Makefile debian/rules
%:
dh "$@"
And the commads not used listed in:
debian/dh_norun
This would be both simple, elegant and maintenence friendly.
Jari
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
