Hi,
It seems I'm late to the discussion on optification in MADDE... In the
earlier discussion, I saw this quote:
> You cannot use that with MADDE, because maemo-optify* commands use
> internally some dpkg* command options that are not implemented by MADDE.
When grepping through the source of maemo-optify 0.2.1, I see no such
calls at all, anyone care to clarify this?
I tried adding the maemo-optify scripts outside of MADDE, in my path (on
OS X), and it seems to work just fine, but the rest of the environment
adds some complications.
dh_fixperms, which write the list of files for tarlisted, doesn't
recognize symlinks at all, but this can be fixed with the attached patch.
This would be an issue also if doing manual optification and using
symlinks, I think?
The final problem, though, is that of the order of commands in
debian/rules, which, for me, initially looked like this:
dh_strip
dh_compress
dh_fixperms
# dh_perl
# dh_makeshlibs
dh_installdeb
dh_shlibdeps
dh_gencontrol
dh_md5sums
maemo-optify
dh_builddeb
dh_fixperms is called a few steps before maemo-optify, so it creates a
.tarlist that references files as they are at that point, but maemo-optify
changes them later on. maemo-optify cannot be called before dh_installdeb,
though. Moving dh_fixperms down to below maemo-optify does seem to work,
although I'm not sure if that's an acceptable change in general.
// Martin--- dh_fixperms_orig 2010-07-02 11:58:45.000000000 +0300
+++ dh_fixperms 2010-07-02 12:04:34.000000000 +0300
@@ -47,6 +47,12 @@
next;
}
+ if (-l $src) {
+ my $dest = readlink($src);
+ tlline '---', "$_ -> $dest";
+ next;
+ }
+
# Programs in the bin and init.d dirs should be executable..
if (m,(^|/)bin/, || m,(^|/)sbin/,
|| m,(^|/)usr/games/, || m,(^|/)etc/init.d/, ) {
_______________________________________________
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
