Hi,
Norbert Preining wrote:
> On Mit, 04 Jul 2007, Rene Engelhard wrote:
> > Yes, there are. And for most dh_ stuff the dh_ scripts *do* figure out
> > that they don't have do do stuff on package foo (like if package foo has
> > no .menu you don't need to add the menu stuff). Even dh_pycentral does
> > that...
>
> Ok, I retitled the bug and removed the wontfix stuff. If I find time I
> will implement it.
Thanks.
(I just added the workaround as that's needed now...)
> > > dh_installtex -p texpower
> >
> > I know that this is possible, I'd call this a workaround, though.
>
> The man page prominently specify:
> > Your package should depend on an appropriate version of tex-common so
> > that the update-* commands are available. (This program adds that
> > dependency to ${misc:Depends}.)
I didn't deny that. Why are you citing this? I know that misc:Depends
should be there, that's why it is for texpower. Just not for
the -examples and -manual packages as those don't have any tex files and
I trusted dh_installtex to behave like the other dh_ stuff..
> Furthermore, if someone uploads a package without trying to build it
> himself in a clean pbuilder/cowbuilder/sbuild/whatever ....
Yes, but that's *completely* unrelated to the issue at hand. Building
in a sbuild didn't prevent anything mentioned here from happening. Of
course, you can blame me for not running piuparts, but...
Gr�gards,
Ren�-
.''`. Ren�ngelhard -- Debian GNU/Linux Developer
: :' : http://www.debian.org | http://people.debian.org/~rene/
`. `' rene@debian.org | GnuPG-Key ID: 248AEB73
`- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73
Attachment:
signature.asc
Description: Digital signature