On Fri, Oct 7, 2016 at 5:19 AM, Fan Xin <[email protected]> wrote: > Hi Joshua, > > Thanks for your info. > > Actually, our origin motivation is that we found smartpm is not maintained > any more. We maintain smartpm for our distro at > https://github.com/ubinux/smart2 > > Then we realize smartpm should switch to python3. In order to solve this > issue, there are four solutions as follows. > > [1] smart/RPM5 > [2] smart/RPM4 > [3] dnf/RPM5 > [4] dnf/RPM4 > > I confirm that RPM5 have some bugs with python3 and I am not familiar with > RPM. So I think the easy way to solve this issue is [2], recover RPM4 and > solve the bugs in smartpm. > >> >> It's also worth pointing out that we're strongly considering dropping >> SMART in the next (2.3) development cycle[4]. >> > Considering YP would like to drop smart in 2.3, I wonder YP would use > [3]dnf/RPM5 or [4]dnf/RPM4 ?
BTW. do you recall the rationale behind abandoning zypper in 1.4? I'm curious about the motivation for using smart given its Python dependency. -- Maciej Borzecki RnDity -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
