On Thu, 27 May 2010, Ole Loots wrote:
The other issue with Sparemint (well RPM), at least in my opinion, is architecture support. By default, unless currently noted, RPMs are built for a 68000 target. Should that remain the same, or should this expand so that packages are also target at 68020-60 and then later at the Coldfire? If so, how?I would like to see architecture optimized RPM's. I don't care how it's done (right now), and I don't know how it could be done. But I think there should be an clean and straight way for targeting different architectures + installing for different architectures.
We are fine for 'most' packages in SpareMiNT for the development libraries as they live in their own homes in /usr/lib for the 2, now 3, different archs. /usr/lib for 68000, /usr/lib/m68020-60 for 020-60, and now /usr/lib/m5475 for Coldfire. Now they would just need to be built! :)
The issue arises, if you wish to call it that, for the binaries. Although, I personally see no reason to separate the binaries based on architecture on an installed system, I do see the advantage of binaries targeting specific CPUs.
I guess I'll scribble together my thought for doing this since I have been screwing around with this some for Sparemint.
Keith