From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: Fan Xin <fan.xin@jp.fujitsu.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: rpm: Recover RPM4 to OE-core
Date: Tue, 11 Oct 2016 15:05:45 +0100 [thread overview]
Message-ID: <1476194745.2912.27.camel@linux.intel.com> (raw)
In-Reply-To: <354af725-27e7-ba35-2a45-514151904c32@jp.fujitsu.com>
On Fri, 2016-10-07 at 12:19 +0900, Fan Xin 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
Indeed, the lack of maintenance for Smart is one of the reasons we're
looking to switch away from it.
> 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 ?
There are two main reasons we want to switch away from Smart. Firstly
we made a concerted effort to switch to Python3 in the 2.2 cycle —
Smart is one of the few recipes in OE-Core which still pulls in
Python2, maybe the only one we use by default (for RPM using distros).
Secondly Smart is unmaintained and has several known issues related to
its abstraction over package backends.
So far as I'm aware no decision has been made as to what we'll replace
Smart with yet. I believe the first step will be to investigate RPM5 &
dnf.
Regards,
Joshua
prev parent reply other threads:[~2016-10-11 14:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 11:18 rpm: Recover RPM4 to OE-core Fan Xin
2016-10-06 12:42 ` Joshua Lock
2016-10-07 3:19 ` Fan Xin
2016-10-07 7:20 ` Maciej Borzęcki
2016-10-07 9:52 ` Fan Xin
2016-10-07 10:39 ` Maciej Borzęcki
2016-10-07 15:52 ` Richard Purdie
2016-10-11 14:05 ` Joshua Lock [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1476194745.2912.27.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=fan.xin@jp.fujitsu.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.