Hi,
Let me elaborate how to use try06 and try07.
First some background.
Use of try06 ensures that binary rebuild of package ensures to use the
latest autotools. If you use try07, it will lock source to today's
autotools. So I think it is #2 choice.
The big patch in try07 is only meant as proof-of-concept that this big
patch method can be used to update source to match autotools in that
particular distribution. I have no idea what happens if we use this one
created by new autotools interfare with old ones when you backport
package. I think running "autoreconf -i -f" under appropriate cheroot
to make similar patch may be better idea. If you do not like
dh-autoreconf, another idea is to use:
override_dh_auto_configure:
autoreconf -i -f
dh_auto_configure
This may be the best solution for older Ubuntu. So this is #2 choice.
Another reason I do not like try07 patch is I did not include all
generated files. I just guessed these are the ones needed and seems to
work.
I think updating these generated file in upstream needs to be done
carefully since it may cause extra work for other distribution. For
example, if others had tried similar thing as try07, such patch to
upstream breaks build of such packages.
(I know these negatives are small. As long as I do not need to defend
this patch, you are free to use try07 method or pushing it to upstream.
I just do not have enough knowledge.)
Osamu
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
