OpenWrt Forum Archive

Topic: A bit of help with ipkg please ?

The content of this topic has been archived on 7 May 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi,

I have some simple code added via the documented route as a package to kamikaze, and it builds with the executable present when it tftps to the target linksys box.

Have it got it right that you can just upload the package to the linksys via the ipkg command, rather than building and flashing the whole router each time?

I have tried hacking the /etc/ipkg.conf to point to my devel box web server and done the ipkg list, but when I try to install my package I get

'root@OpenWrt:/usr# ipkg install mcast
Installing mcast (1.0-1) to root...
Downloading http://192.168.1.2/packages/./mcast_1.0-1_mipsel.ipk
Nothing to be done
Done.
Collected errors:
Package mcast md5sum mismatch. Either the ipkg or the package index are corrupt. Try 'ipkg update'.


But I have removed the package, so its not present.

Some instruction on the basics to getting this to work would be good !

Thanks

nick

It looks like the ipkg.conf changes you made were effective. It is obtaining the package from your 192.168.1.2 system.

After any change to the ipkg.conf you'll need to do an "ipkg update". Did you already do that? If you did then I suspect there are problems with the package itself or maybe the package repository index on your 192.168.1.2 system.

Hi Pric0112,

Thanks, it sounds like I'm getting somewhere.

My makefile for the package does not have an MD5 checksum - does it need one (and how?)?

Also for this to work do you have to increment the version number in the makefile, or does it use dates/md5 to 'know' that it needs to update?

Thnak very much

nick

The discussion might have continued from here.