On Fri, Jan 31, 2003 at 08:18:10PM -0500, Matt Zimmerman wrote: > On Fri, Jan 31, 2003 at 05:04:24PM -0700, Chris Larson wrote: > > > Its not simply a matter of arch, there are options specific to the > > machine in question we're targeting, hence those options. > > Indeed, so what we really want for Debian is those options only, e.g. Zaurus > or iPAQ. Builds will always be done natively for the target platform (no > cross-compilation). > > >From my brief look, it seemed that the architecture selection was determined > by the target platform, which is nice, but we'll need to be able to override > it or something. > > How much is different between Zaurus and iPAQ? We'll likely want to provide > packages for both where appropriate.
I've been exchanging emails with Chris since the last post over this and what he has explained is that the only thing we have to worry about when it comes to all of this is libqpe. So what my current plans are to provide different libqpe packages...1 for arm, 1 for sharp, and 1 for ipaq. This means only 2 extra packages. libqpe is the only thing that isn't smart enough to determine hardward specific options on the fly. So unless I completely missunderstood Chris this should work. We'll have a libqpe1, a libqpe1-sharp, and a libqpe1-ipaq. Now...what we may need to do is create some meta packages. one for ipaq and one for sharp that will depend on the proper packages to make up the base system. Ivan -- ---------------- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
