On Fri, Jan 12, 2018 at 05:32:32PM +0100, Pavel Hrdina wrote:
> On Fri, Jan 12, 2018 at 03:43:55PM +, Daniel P. Berrange wrote:
> > On Fri, Jan 12, 2018 at 12:36:23PM +0100, Pavel Hrdina wrote:
> > > On Thu, Jan 11, 2018 at 04:43:35PM +, Daniel P. Berrange wrote:
> > > > Be clear about whic
On Fri, Jan 12, 2018 at 03:43:55PM +, Daniel P. Berrange wrote:
> On Fri, Jan 12, 2018 at 12:36:23PM +0100, Pavel Hrdina wrote:
> > On Thu, Jan 11, 2018 at 04:43:35PM +, Daniel P. Berrange wrote:
> > > Be clear about which distros we aim to support with the specfile, so we
> > > know
> > >
On Fri, Jan 12, 2018 at 12:36:23PM +0100, Pavel Hrdina wrote:
> On Thu, Jan 11, 2018 at 04:43:35PM +, Daniel P. Berrange wrote:
> > Be clear about which distros we aim to support with the specfile, so we know
> > what we can cleanup in the spec later.
>
> Do we really want to have this limitat
On Fri, Jan 12, 2018 at 12:36:23PM +0100, Pavel Hrdina wrote:
On Thu, Jan 11, 2018 at 04:43:35PM +, Daniel P. Berrange wrote:
Be clear about which distros we aim to support with the specfile, so we know
what we can cleanup in the spec later.
Do we really want to have this limitation?
Yes
On Thu, Jan 11, 2018 at 04:43:35PM +, Daniel P. Berrange wrote:
> Be clear about which distros we aim to support with the specfile, so we know
> what we can cleanup in the spec later.
Do we really want to have this limitation? If so, maybe we can alter
the "requires" message to only warn that
Be clear about which distros we aim to support with the specfile, so we know
what we can cleanup in the spec later.
Signed-off-by: Daniel P. Berrange
---
libvirt-python.spec.in | 16
1 file changed, 16 insertions(+)
diff --git a/libvirt-python.spec.in b/libvirt-python.spec.in
i