> for FILE in debian/*.install.in; \
> do \
> sed -e "s/@DEB_HOST_MULTIARCH@/x86_64-linux-gnu/g" $FILE >
> debian/`basename $FILE .in`; \
> done
> dh_install
> sed -i -e 's/@DEB_HOST_MULTIARCH@/x86_64-linux-gnu/g'
> debian/scim/etc/X11/xinit/xinput.d/scim-immodule
> sed: can't read debian/scim/etc/X11/xinit/xinput.d/scim-immodule: No such
> file or directory
> debian/rules:30: recipe for target 'override_dh_install' failed
Any progress on this?
The reason it fails is that we are creating arch-independent packages only,
so debian/scim/[...] does not exist because "scim" is arch-dependent.
But this should be very easy to fix: Why don't you just split
dh_install into dh_install-arch and dh_install-indep?
While we are at it, some comments about debian/rules:
* The first "for" loop and the different .in files are probably
unnecessary if you just use something like this in the *.install
files:
usr/lib/*/libscim-*[!ao]
(that would be directly libscim8v5.install, without .in suffix)
i.e. dh_install supports multiple wildcards in *.install files.
* Using "set -e" alone in a single line in debian/rules is useless
because debian/rules is a Makefile and each line is executed in
a separate shell. Just try this minimal Makefile and you will see
what I mean:
all:
set -e
false; true
echo Hi
If you use "set -e" in a Makefile you would have to put it in
the same line as the shell code for which you want "set -e"
to work.
In this case, however, you can drop each and every "set -e":
* The one in override_dh_auto_install because it has no effect at all.
* The one in override_dh_install may be dropped if you just omit the .in
files and use multiple wildcards in *.install files, as explained before.
Thanks.
