Closed GoogleCodeExporter closed 9 years ago
Issue 66 has been merged into this issue.
Original comment by paul.betafive
on 18 Sep 2013 at 1:10
Forcing a reinstall shouldn't brick the system. I know this was reported a
while ago, do you know if this is still an issue? I'll add it to my todo list
to look into.
Original comment by paul.betafive
on 18 Sep 2013 at 1:12
Original comment by paul.betafive
on 18 Sep 2013 at 1:14
I have a potential idea for solving this. When reinstalling with
"--force-reinstall", we could add a suffix to the version of the package to be
installed, such as ";__r1" for the first reinstall, ";__r2" for the second,
etc. This suffix should be safe from clashes with the ending of any sensible
version string.
So if we run "opkg install --force-reinstall a" and a is installed at version
1.0, we would read the package control fields for a using pkg_init_from_file(),
modify the version string to append or increment the reinstall suffix and then
insert it into the pkg hash table using hash_insert_pkg(). This would
effectively be a modified flow of opkg_prepare_url_for_install().
With this behaviour the version strings wouldn't actually match and so the
reinstall would be seen as an upgrade. The trick would simply be to hide the
reinstall suffix whenever a version string is printed for the user.
Original comment by paul.betafive
on 10 Feb 2014 at 9:19
I've taken a different approach to that listed in the previous comment but this
is now fixed and confirmed with test cases in both the opkg-0.2.x and master
branches.
Original comment by paul.betafive
on 1 Mar 2014 at 3:10
Thank you Paul!
Original comment by Martin.J...@gmail.com
on 1 Mar 2014 at 3:43
Original issue reported on code.google.com by
Martin.J...@gmail.com
on 17 Dec 2010 at 8:23