My Opie Does Not See Ipkgs

[togomenu]

Any ideas why my Opie (newest) running under OpenZaurus (newest) on a Sharp 5500 does not see the packages on my cf card?  When I open the package manager I see the default packages installed in Opie and they are all blue (installed).  How do I get the newer packages that I dl to show up on the Package Manger screen to install?  This has worked for me under Qtopia/SharpROM in the past, but this is my first foray into Opie.  Am I doing something wrong?

Oh, I can access the files under the doc tab and when I click on them the Package Manager opens up , but they are not listed (red).

Any ideas or advice on this?

Thank you!

[lardman]

I thought this had been fixed, but it's a problem with the GUI package manager. Try using ipkg from the command line, or creating a local feed for your packages on the CF card.


Si

[GenericAnimeBoy]

Welcome to the OZ community, togomenu.

Package management and installation in OZ is different than in the other roms.  The Opie packagemanager is not in a finished state just yet, AFAIK.  Here's how to install packages; because it seems to me like there's not a clear, plain language post about this yet that contains all of the necessary information, I'm going to go step by step.

First, connect your Z to the internet, if you can.  If you can't, that complicates things quite a bit.  In that case, scroll down to the bottom for further directions.

PACKAGE INSTALL DIRECTIONS FOR INTERNET ACCESSIBLE ZAURUS USERS
Then, use the ipkg command from the command line as follows:

Code: [Select]

> ipkg -d (destination--usually 'sd', 'cf' or 'ram') install (packagename)
ipkg then goes online and finds the package you asked for on the feeds listed in it's config file /etc/ipkg.conf.  It automagically downloads the package and all of the other packages it depends on and installs them to the location you specified with -d (destination).  Possible destinations, btw, are 'root', 'ram', 'sd', or 'cf', without the quotes, of course.

So.  To install mplayer (movie player) on your cf card, you would type:

Code: [Select]

> ipkg -d cf install mplayer
If all has gone well, the package has been unpacked and installed on your cf card, or wherever you installed it.  But now, in order for the program's shortcuts to show up in opie, the files have to be linked into the proper system directory.  Fortunately, there is another automagical command.  Go back to the console and type:

Code: [Select]

> ipkg-link add (packagename)This usually must be done with each package installed, including dependencies.  An easier way to make sure everything gets linked is to use:

Code: [Select]

> ipkg-link mount (full path to package destination)
So to link our example installation of mplayer, type:

Code: [Select]

> ipkg-link mount /mnt/cf/packages
The package management system works this way (taking packages from the internet, that is) because it allows packages to all use a standard set of libraries which are stored, updated, and installed separately, thus streamlining the updating process whenever new versions of things are released, and allowing some much more powerful and diverse applications.  

It wasn't immediately clear to me, either, that the packagemanager in opie is designed to work directly from the internet feeds.

---------

LOCAL FEED CREATION FOR NON-INTERNET CAPABLE ZAURII
If you don't have internet access on your Z, you are at a slight disadvantage, but never fear.  If you can't take your Zaurus to the feed, you just have to take the feed to your zaurus.  

To make a feed on your CF card, copy the ipk's of the programs you want to install into directories named after the feeds you found them in (opie feed packages in /feeddir/opie, etc.  Also, download the file named "PACKAGES" for each feed directory.  Alternatively, you could lump all of the packages into one directory and use ipkg-utils to make the PACKAGES file, as desribed here.  Then, change the paths in /etc/ipkg.conf to point to your local feeds instead of the internet ones.

Code: [Select]

It will say:
src (feed name) (http://openzaurus.org/official/unstable/3.5.3/feed/(subdir name))

change it to read:
src (feed name) (file:///(full path to directory))
After you make the feeds and have all of the ipks you need, including all of the dependencies, simply install packages as described above (in the internet capable section)

I don't think I explained that very well, but again, reading this thread might help a little.

I know this seems really complicated, but it's worth it.  Stick with it, and I think you'll find that OZ is a quite good way to go, and it's getting better all the time.

[togomenu]

Ok, so if I "ipkg install something.ipk" the next step would be to create an icon associating, right?  

I get some weird "no file" errors when I try this.  How would one setup a local feed from the cf?
I'll dig about in the package manager.

Right now I'm learning, the only ROM I know of left to try is Cracko.  Is it worth the trouble?  GPE was a little... cludgy, I guess.  I felt like I was in a muddy version of Puppy or stripped Gentoo.

[GenericAnimeBoy]

Sorry if my directions seemed a little ovesimplified to you, as I'm writing for total linux n00bs like myself.  To install a local .ipk file (without a feed or anything), it's

Code: [Select]

> ipkg -d (dest) install (full path to file)/(filename.ipk).However, this won't handle dependencies properly, so your best bet is to go with a local feed.

When you do use a feed, the package name you'll use with ipkg is the one listed for it in the PACKAGES file, not the actual *.ipk filename.

[togomenu]

Thank you for the great data!  I am working on the local feed.  I changed the conf file.  One more quick question though:

I point the ipkg to the cf/opie (my ipk's, no online features yet) and realized there was a thematic within the threads of "original paths".  I clumped 14MB of ipkg's into one directory on the cf thinking that the OZ was similar to the Sharp and intended to install from that.  Am I correct in assuming that I would need to remake these ipk's into one or set up a unique path for each ipkg in stead of clumping them?

[togomenu]

"When you do use a feed, the package name you'll use with ipkg is the one listed for it in the PACKAGES file, not the actual *.ipk filename."

Yeah... um, that would make things smoother.  heh

[GenericAnimeBoy]

Thank you for the great data!  I am working on the local feed.  I changed the conf file.  One more quick question though:

I point the ipkg to the cf/opie (my ipk's, no online features yet) and realized there was a thematic within the threads of "original paths".  I clumped 14MB of ipkg's into one directory on the cf thinking that the OZ was similar to the Sharp and intended to install from that.  Am I correct in assuming that I would need to remake these ipk's into one or set up a unique path for each ipkg in stead of clumping them?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=77241\"][{POST_SNAPBACK}][/a][/div]

To set up the local feed, I copied the files from the online feed into paths named after the online feed they came from, eg. "../official/unstable/3.5.3/feed/opie/mplayer.ipk" would get copied to "(path_of_card)/feed/opie", and "../official/unstable/3.5.3/feed/libs/sword" would get copied to "(path_of_card)/feed/libs".  Then copy the PACKAGES files from the feeds to your card.  Each subdirectory (opie, libs, etc) will have its own PACKAGES file.

[lardman]

Don't forget, that after adding a new feed (or when first using ipkg), you need to allow ipkg to grab a package list by running:

'ipkg update'

This downloads a list of all the available packages in all the feeds you have setup. If you don't do this, ipkg will say it can't find the file, and even suggests that you do update.


Si

P.S. Also note that OZ can now use Packages.gz files (which are compressed) which reduces the amount of data which needs to be downloaded.