I'll respond to these and then ask you to stop posting here, since you clearly have no interest in the project, but a lot in causing bother.
If I didn't care I wouldn't post!
Like I said I was initially in favour. It's just the details put me off.
Firstly, there is nothing special about the deb format.
There's nothing special about pretty much any package format I've ever used (except perhaps .msi, but then microsoft often tend to over-engineer stuff). That's not the point.
gp2x is a unique platform that needs a unique solution. Nobody is going to be copying dpkg files between debian and and the gp2x... there's no point in much of the baggage that dpkg files store (even ipkg tends to assume that you can do things like install to /lib and /bin). Stick a tarball of the binary in there and a single file describing the version, author, description etc., maybe an install script (although they should be rare) and you've got all you need.
If you want to stick that in a .ar file and call it dpkg then fine (although I'd recommend calling it something else) but at least ship an app that'll open it in different OS's if you do that (btw. winrar cannot open .ar files.. outside cygwin I'm not aware of anything on windows that will).
which would be silly since as I said before, debs are already a standard. Nobody is forcing you to use GPIs,: continue to use zips if you want, or extract the data from GPIs (it isn't hard, I could explain it in a few lines
A lot of developers are going to release their downloads in one format. Why would they bother making two? So you're faced with two outcomes - 1. most people keep using zip, or 2. most people move to the new system.
If I can double click on one of your GPI files and it opens and I can drop stuff on the SD like I do now then I'll be happy (well actually I install into an image onto the NAS which is about 6gb of stuff and won't fit on an SD, but it's the same principle).
As for usb/eth on Windows, I have actually done it many times before (the exact procedure I can't remember anymore, but it wouldn't be hard for me to look up) with the iPAQ/Familiar Linux and it takes
about 2 minutes to configure (which I am quite capable of documenting).
The HOWTO sends you to microsoft's site downloading windows 2000 specific SDKs, which of course doesn't work at all. It also suggests you hand-craft a .inf file..
Yes you don't need to do that but I wasted about half a day on it before I gave up and worked it out for myself (find a working .inf, select 'update driver' and let the system pickup its default drivers. Even got that working for 64bit with a bit of hacking).
I wonder how many 'ordinary' users could even handle the network setup TBH... never overestimate the knowledge of your users.
You need to understand that developers work on whatever they want, not what somebody tells them they should be working on because they think it would be more 'worthwhile' (this is something we've seen more of
I know - I've worked with developers (and developed stuff) for 15 years... Nobody's saying you haven't got a good idea. A proper package system could work well. That doesn't stop me having opinions about 'proper' though