Closed GoogleCodeExporter closed 8 years ago
"after i rebuild package from source with different options but version is not
increased, there's no easy to re-install it"
Don't do that, increment the version or create a differently named package
which Conflicts with, or Replaces the old one. Or regenerate your package index.
"with --force-reinstall, opkg remove the old before it install a new package"
Yes, its not ideal, but this design decision was taken years ago with ipkg
because it was intended for systems with very small amounts of flash.
Original comment by graham.g...@gmail.com
on 7 Oct 2010 at 10:28
"regenerate package index" is not an alternative option, it's a must do step
options could be enable/disabled in Config.in in make menuconfig, and ppl would
like to switch between kernel/gcc/eglibc/glibc versions and toolchain can also
possible affect some build bugs and fixed later. package version are not aware
of these settings.
different kenerl config change is the most important, if you failed to upgrade
all kmod-* and kernel file to same version, you might stuck at boot up. but
after days i figure this issue out, i find it hard to do a reinstall them by
using opkg
when you introduce --force-reinstall, you know it's needed. --force-upgrade (or
whatever you name it) is just an alternative way for --force-reinstall
implementing --force-upgrade is easy i guess, simply assume the old version is
0 or simply upgrade to same version
Original comment by xue...@gmail.com
on 8 Oct 2010 at 3:24
"with --force-reinstall, opkg remove the old before it install a new package,
this is horrible if it try to reinstall busybox/bash/wget/opkg etc"
This is the real problem here. --force-reinstall shouldn't brick the system,
then a --force-upgrade wouldn't be needed.
Original comment by paul.betafive
on 18 Sep 2013 at 1:10
Original issue reported on code.google.com by
xue...@gmail.com
on 7 Oct 2010 at 9:41