Hi For the 'ptxdist images' run, ipkg files from PKGDIR are used, which do not have a -1 suffix attached.
The ipkg-repository created by ipkg-push creates a dist of the same files and attaches a -1..n suffix to the version part of the ipkg filename for each file. When booting from a flash image and after an update with ipkg this looks like packet updates and 'ipkg upgrade' would download and (re-)install the same files again. So we need to - either reintroduce IMAGE_FROM_IPKG_REPOSITORY, which means to use the configured ipkg-repostory instead of PKGDIR after a ipkg-push to construct the other images (tgz, jffs2, ...). Now, after ipkg-push is fully functional (just tested), this would be a viable option. Unfortunately ipkg-push is really slow and a bit useless within a dev environment. But fine for updating selftest and burn-in software on our hard with a cron job as needed. - or, create a dist/... directory tree within PKGDIR with a simple script, so that all ipkg files have at least a -1 attached to their version and create the Packages.* file at the expected place within the /dist/... tree. This would be much faster, but lacks versioning and requires some --force flags to 'ipkg install', if you created a new package. This would be acceptable within a dev environment to update stand-alone non-nfs boxes and test the changes before ipkg-push is used to create an incremental release in your ipkg-repository, e.g. release a new burn-in test packet to all boxes in the lab. So probably both options would be a good idea and I can imaging many nice use-cases. For nfs-mounted systems this issue is of course a 'don't care'. Any comments? Carsten -- ptxdist mailing list [email protected]
