On Wed, Aug 12, 2009 at 12:58:53PM +0200, Hector Oron wrote:
[PACKAGES]For Crush 2.0 (before multiarch), *it is not worth it to work on it*, with current approach, it is too much time consuming (Neil has already pointed out some of the drawbacks). But it is better to work for Crush 3.0.
Could someone please point me to documentation/diff betwen 2.0 and 3.0?
But, Neil, what do you think on having a debian/rules which points to debian/rules.d/$native_rules if DEB_BUILD_ARCH == DEB_HOST_ARCH and debian/rules.d/$cross_rules if DEB_BUILD_ARCH != DEB_HOST_ARCH? With this and xcontrol, we might be able to make it possible and easy for crush 2.0, but as you said it might not worth the time if everything changes.
This sounds odd: You want to rewrite packaging scripts for *all* packages that needs cross-compiling? Or when would above make sense?
Kind regards, - Jonas -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
Attachment:
signature.asc
Description: Digital signature