Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - drw

Pages: [1]
1
Angstrom & OpenZaurus / New Konqueror (or Other Browser For Opie)
« on: April 22, 2005, 03:30:52 pm »
Konq/E is built upon Qt/E 2.3.x, and back when KDE was using Qt 2.x, it was fairly easy to support both the KDE and Qtopia/Opie versions from a single code base.  However, KDE has moved on to newer versions of Qt and newer versions of Konqueror no longer compile against Qt/E 2.3.x.  So while there have been bug fixes made to Konq/E, newer features have not been back ported to the older code base, and I don't see that happening any time soon.

So next you will probably ask why Opie still uses an ancient version of Qt/E?  Well, TrollTech itself has admitted that Qt/E 3.x is not really suited to use in limited resource devices such as PDA's.  And though Qt/E 4.0 is supposed to be much better, we are still waiting for a pre-release version which compiles/works.

2
Angstrom & OpenZaurus / Ipkg Cannot Find Local Ipks
« on: April 02, 2005, 01:07:52 pm »
Quote
Alright, getting very fed up now.
Can somebody please tell me what is wrong with this ipk?

control/control:

Package: irppp
Section: opie/Shell
Priority: optional
Maintainer: Simon Williams <www.systemparadox.tk>
Architecture: arm
OE: irppp-1.0.0
Version: 1.0.0
License: GPL
Description: Simple Opie-SH script to start/stop a PPP over IrCOMM connection.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=73263\"][{POST_SNAPBACK}][/a][/div]

Make sure that that architecture is defined in either /etc/ipkg.conf or /etc/ipkg/*.conf files.  In one of those files, there should be a line similar to the following:

arch arm 16

'arch' is a keyword identifying this as a architecture configuration item
'arm' is the type of architecture (make sure you have one arch item which matches the architecture in your package's control field)
'16' is a priority value for this architecture (I believe higher value has higher priority).  The value decides which arch takes precidence over another.

If you don't have the arm arch defined, add it to /etc/ipkg.conf.

3
Angstrom & OpenZaurus / Package Manager In 3.5.2
« on: March 27, 2005, 05:45:00 pm »
The feeds for OZ3.5.2/Opie are:

src/gz Base http://openzaurus.org/official/unstable/3.5.2/feed/base
src/gz Console http://openzaurus.org/official/unstable/3.5.2/feed/console
src/gz Devel http://openzaurus.org/official/unstable/3.5.2/feed/devel
src/gz Libs http://openzaurus.org/official/unstable/3.5.2/feed/libs
src/gz Opie http://openzaurus.org/official/unstable/3.5.2/feed/opie
src/gz Unknown http://openzaurus.org/official/unstable/3.5.2/feed/unknown

You can either add each one in manually to Opie Package Manager in the Servers tab of the configuration dialog (make sure and check the 'Compressed Feed' item for each one), or copy and paste the lines above directly into /etc/ipkg.conf.

For konqueror, install libpcre first.  Then install konqueror with the Force Depends option ('ipkg install konqueror -force-depends' if working from the command line).

Also, you might want to subscribe to the openzaurus-users mailing list and/or check out its archives.  This and many other questions have been answered before.  The links to the mailing list archive and subscription page are on the openzaurus.org site.

4
Angstrom & OpenZaurus / Openzaurus 3.5.3 Pre-release
« on: March 26, 2005, 05:23:46 pm »
I have uploaded an Opie c7x0 image and feed to:

http://oz.hentges.net/snapshots/3.5.3-1/c7x0/

Please checkout the README for updating the ipkg feed directory.

Enjoy!

5
Angstrom & OpenZaurus / Openzaurus 3.5.3 Pre-release
« on: March 24, 2005, 03:39:09 pm »
CoreDump,

I will be glad to do an Opie/clamshell build after we tag Opie 1.2.0 (plan on doing it anyway for my device), probably Saturday.  Would I be able to put the image/feeds up on your site?  If not, I can probably add it on my handhelds.org home dir.

Dan

6
Angstrom & OpenZaurus / Oz Package Management
« on: March 22, 2005, 08:18:29 pm »
I assume you are referring to the Opie Package Manager as opposed to the GPE one.

Generally, Opie's Package Manager (Opie PM) is stable as long as you limit the number of commands you execute.  Due to a memory leak in libipkg, which Opie PM uses, each command allocates an additional 1-2 Megs of RAM which is not freed until the program is exited.  Once your device's free memory has been used up, Opie PM will crash, which could cause problems if it was in the middle of doing something.

The maintainer of libipkg is aware of the issue, and newer versions of libipkg have improved the situation somewhat (newer version will be included in the next version of OZ).

I believe your device has 32 Meg of RAM, so with no other programs running, you can probably do about 4 installs/removals before you will need to close it down and restart it.  One thing I have done in the past is to have System Info running (using the 1st tab, 'Memory') at the same time so I can monitor the memory useage.

The other option is to use the command line utility, ipkg.  However, if installing apps to a SD/CF/MMC card, you will need to also run ipkg-link to set up the appropriate links.  Also, Opie will need to be restarted for any newly installed apps to appear in the Launcher.  Opie PM does these things automatically for you.

7
Angstrom & OpenZaurus / Package Manager
« on: February 08, 2005, 11:04:02 am »
Quote
This sounds interesting (like I said, I use the command line ipkg).  I think I'm gonna give this a shot.

But two questions (sort of):

1.  In another thread someone mentioned the last CVS version of the package manager installs package deps to RAM and not the location of the initial package being installed.  Does the one in upgrades fix this?
Not that I am aware of, the problem is/was dependent packages were not being linked at all.  This is fixed in the upgraded version.

Quote
2.  What on earth is a compressed feed?  (Is it a .gz version of an entire feed directory?  Cuz' that would make downloading a whole feed WAY easier than what I'm doing using a dir grabber to grab all the files...)  And if it is this, where do I get it?
An ipkg feed normally uses a file, named Packages which is a plain text file containing the information about each package in that feed.  A compressed feed is one where this file is compressed (saving download time when doing an 'ipkg update').  Once this file is downloaded to your device, it is saved in uncompressed form, so does not save any ROM space over a regular feed.

8
Angstrom & OpenZaurus / Packagemanager Links To Ram(3.5.2)
« on: February 08, 2005, 10:54:06 am »
This was a known issue that was fixed in December.  It wasn't just when installing to RAM, but when dependent packages were being installed to any destination.

9
Angstrom & OpenZaurus / Package Manager
« on: February 04, 2005, 04:35:31 pm »
Quote
I am aware that this is the unstable tree, but I can't see any way at all that opie-packagemanager is better or more stable than aqpkg, or any way it succeeds it- apart from (probably) being written after.

If you do want more features in the packagemanager (and there are currently more features in aqpkg), why aren't you adding them to aqpkg rather than writing a whole packagemanager from scratch?

(I sure hope it isn't more stability you are looking for- the irony would too much)
(though I haven't tried the upgraded packagemanager yet)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=65580\"][{POST_SNAPBACK}][/a][/div]

Can you please tell me what features aqpkg implements that opie-packagemanager does not?

Currently, opie-packagemanager has more features than aqpkg, such as support for compressed feeds (src/gz, used by Familiar, OZ), better package filtering (based on things like: source feed, installation status, installed to destination, etc.), native package linking (do not require ipkg-link with its problems).  Plus there are fixes to many of aqpkg's shortcomings in regards to UI, package version comparisons and interface with ipkg.

Now I realize that there are some stability issues currently.  There have been memory leaks identified in libipkg which causes most of the problems.  One developer has sent a patch to the maintainer of libipkg, with no response (that I am aware of).  This is not to lay blame elsewhwere, but to let you know that we are aware of the issues and are trying to resolve them.

Also, as the maintainer of aqpkg and creator of opie-packagemanager, I can tell you first-hand that aqpkg's code was a mess (and part of that blame is mine).  Opie-packagemanager in reality uses much of the original aqpkg code, just reorganized and structured much better.  It has allowed me to implement new features much quicker than would have been possible with aqpkg.

Please try the latest version of opie-packagemanager, it fixes package linking, supports the compressed feeds and has some other UI tweaks/improvements.

drw

10
Angstrom & OpenZaurus / 3.5.2 Upgrades
« on: February 04, 2005, 03:42:07 pm »
Can you add opie-tetrix? - fixed layout for large screens.

Thanks!
----
drw

Pages: [1]