At 18:40 02.03.2002 -0700, Micah Dowty wrote: >Good idea. >Config files would definitely have to be in a device-specific package too. >It's looking like we'd have files for pgserver and pgserver.conf that are >architecture-specific and device-specific, applications that are >architecture-specific, and things like theme files that are completely >platform-independant. > >On Sun, Mar 03, 2002 at 01:57:20AM +0100, Thomas A. de Ruiter wrote: > > Since ipaq, zaurus, psion are all arm... Could we make a 'distribution' > for picogui in ipkg form... So just only the picogui packages... > Something we could add to the /etc/apt/sources.list of the ipkg system... > I think the only thing that differs is the server so we could make a > pgserver-zaurus, pgserver-ipaq, pgserver-psion etc... packages and only > one pterm package that can be used for all... ;) > > AFAIK, the PSIONs are armv3 and �cLibc, while iPAQ and Zaurus are armv4 and glibc, so they are not binary compatible. For the two armv4 systems, I wouldn't even bother building different server packages, since the hardware specific drivers are really small considering the available flash memory. Maybe it's even a good idea to just put both configuration files into the ipk file for the server and let a postinstall script decide which one is put into /etc/pgserver.conf.
I could make experimental packages when I get back to my workstation (maybe next week), but I wonder if it is possible to build them automatically like the documentation currently is. BTW: What exactly are the PSION machines running, is it also some familiar/ipkg based distro or something completely different? Arnd <>< _______________________________________________ Pgui-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/pgui-devel
