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 completel
Nifty.
Yes, we could use ipkg support for PicoGUI on the Zaurus too :)
Wow, PicoGUI's list of supported hardware is growing..
On Sat, Mar 02, 2002 at 06:07:33PM +0100, Arnd Bergmann wrote:
> Hi,
>
> I just got myself an iPAQ and since PicoGUI had no support for its
> touch screen, I wrote a s
Am Samstag, 2. März 2002 23:51 schrieb Mark Blunier:
> I had more source errors when I ran make menuconfig so I relinked
> /bin/sh from ash to bash, and then make menuconfig worked as well.
Well, it is still a bug that has to be fixed in PicoGUI. I'm sending
this to the list again so that some
Am Samstag, 2. März 2002 22:11 schrieb Mark Blunier:
> checking if the configuration file is readable... profile.user
> source: not found
> configure: error: problem while parsing configuration
> Bash-2.05a$
>
Hmm, looks like something funny is going on with your shell. The
`source' command is
I'd like to experiment with pgui, but I'm having trouble
installing the source. I've downloaded the source, but I
get an error following the INSTALL directions. I'm running
the latest versions of automake, autoconf and libtool in
Debian Woody. Heres the output of autogen.sh and
./configure. An
Hi,
I just got myself an iPAQ and since PicoGUI had no support for its
touch screen, I wrote a simple driver for it and committed it to
the CVS. I still could not make the keys work, but apart from that, it
works as expected.
Is anyone already working on ipkg packages? If we have those, we can
