Re: F31 System-Wide Change proposal: Automatic strict inter-package dependencies

2019-02-25 Thread Zbigniew Jędrzejewski-Szmek
On Sun, Feb 24, 2019 at 09:42:10PM -0500, John Harris wrote: > On Saturday, February 23, 2019 7:21:36 PM EST Richard W.M. Jones wrote: > > On Mon, Feb 18, 2019 at 08:26:58PM -0500, Neal Gompa wrote: > > > > > On Mon, Feb 18, 2019 at 6:31 PM Tom Stellard wrote: > > > > > > > > > > > > > > >

Re: F31 System-Wide Change proposal: Automatic strict inter-package dependencies

2019-02-24 Thread John Harris
On Saturday, February 23, 2019 7:21:36 PM EST Richard W.M. Jones wrote: > On Mon, Feb 18, 2019 at 08:26:58PM -0500, Neal Gompa wrote: > > > On Mon, Feb 18, 2019 at 6:31 PM Tom Stellard wrote: > > > > > > > > > > > Would there be some way to opt out of this? In some cases, > > > %{name}-devel >

Re: F31 System-Wide Change proposal: Automatic strict inter-package dependencies

2019-02-23 Thread Richard W.M. Jones
On Mon, Feb 18, 2019 at 08:26:58PM -0500, Neal Gompa wrote: > On Mon, Feb 18, 2019 at 6:31 PM Tom Stellard wrote: > > > > Would there be some way to opt out of this? In some cases, %{name}-devel > > Requires only %{name}-libs and not %{name}. > > > > Perhaps it's not obvious, but the idea here

Re: F31 System-Wide Change proposal: Automatic strict inter-package dependencies

2019-02-20 Thread Petr Pisar
On 2019-02-19, Petr Pisar wrote: > I have a few packages that use "virtual provides" provided by multiple > subpackages to allow users to select an implementation that best fits > his needs. See perl-Archive-Extract for an example. > > How would you cope with this use case? > If the virtual

Re: F31 System-Wide Change proposal: Automatic strict inter-package dependencies

2019-02-19 Thread Igor Gnatenko
On Tue, Feb 19, 2019 at 4:26 PM Petr Pisar wrote: > On 2019-02-18, Ben Cotton wrote: > > Let's take graphene as an example. > > > > Spec file contains: > > > > %package devel > > Requires: %{name}%{?_isa} = %{version}-%{release} > > %package tests > > Requires: %{name}%{?_isa} =

Re: F31 System-Wide Change proposal: Automatic strict inter-package dependencies

2019-02-19 Thread Petr Pisar
On 2019-02-18, Ben Cotton wrote: > Let's take graphene as an example. > > Spec file contains: > > %package devel > Requires: %{name}%{?_isa} = %{version}-%{release} > %package tests > Requires: %{name}%{?_isa} = %{version}-%{release} > > > What we see when we build RPMs is: > * graphene-devel

Re: F31 System-Wide Change proposal: Automatic strict inter-package dependencies

2019-02-19 Thread Panu Matilainen
On Mon, Feb 18, 2019 at 9:21 PM Ben Cotton wrote: == Dependencies == RPM changes are needed. Will be handled by Proposal Owners. As with the other rpm change proposal, this change was submitted without prior communication with the primary rpm maintainers, so I think a clarification is

Re: F31 System-Wide Change proposal: Automatic strict inter-package dependencies

2019-02-18 Thread Miro Hrončok
On 19. 02. 19 8:17, Igor Gnatenko wrote: I've updated wiki page with what Neal said. Thanks. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to

Re: F31 System-Wide Change proposal: Automatic strict inter-package dependencies

2019-02-18 Thread Igor Gnatenko
I've updated wiki page with what Neal said. On Tue, Feb 19, 2019 at 8:11 AM Miro Hrončok wrote: > > > On 19. 02. 19 2:26, Neal Gompa wrote: > > On Mon, Feb 18, 2019 at 6:31 PM Tom Stellard > wrote: > >> > >> Would there be some way to opt out of this? In some cases, > %{name}-devel > >>

Re: F31 System-Wide Change proposal: Automatic strict inter-package dependencies

2019-02-18 Thread Miro Hrončok
On 19. 02. 19 2:26, Neal Gompa wrote: On Mon, Feb 18, 2019 at 6:31 PM Tom Stellard wrote: Would there be some way to opt out of this? In some cases, %{name}-devel Requires only %{name}-libs and not %{name}. Perhaps it's not obvious, but the idea here is that RPM will "sense" what the

Re: F31 System-Wide Change proposal: Automatic strict inter-package dependencies

2019-02-18 Thread Neal Gompa
On Mon, Feb 18, 2019 at 6:31 PM Tom Stellard wrote: > > Would there be some way to opt out of this? In some cases, %{name}-devel > Requires only %{name}-libs and not %{name}. > Perhaps it's not obvious, but the idea here is that RPM will "sense" what the name of the subpackage it depends on is,

Re: F31 System-Wide Change proposal: Automatic strict inter-package dependencies

2019-02-18 Thread Tom Stellard
On 02/18/2019 12:18 PM, Ben Cotton wrote: > https://fedoraproject.org/wiki/Changes/Automatic_strict_inter-package_dependencies > > = Automatic strict inter-package dependencies = > > == Summary == > Implement feature in RPM which will enforce strict dependencies > between subpackages

Re: F31 System-Wide Change proposal: Automatic strict inter-package dependencies

2019-02-18 Thread Dridi Boukelmoune
On Mon, Feb 18, 2019 at 11:00 PM Miro Hrončok wrote: > > On 18. 02. 19 21:18, Ben Cotton wrote: > > https://fedoraproject.org/wiki/Changes/Automatic_strict_inter-package_dependencies > > > > = Automatic strict inter-package dependencies = > > > > == Summary == > > Implement feature in RPM which

Re: F31 System-Wide Change proposal: Automatic strict inter-package dependencies

2019-02-18 Thread Miro Hrončok
On 18. 02. 19 21:18, Ben Cotton wrote: https://fedoraproject.org/wiki/Changes/Automatic_strict_inter-package_dependencies = Automatic strict inter-package dependencies = == Summary == Implement feature in RPM which will enforce strict dependencies between subpackages automatically (right now

Re: F31 System-Wide Change proposal: Automatic strict inter-package dependencies

2019-02-18 Thread Fabio Valentini
On Mon, Feb 18, 2019 at 9:21 PM Ben Cotton wrote: > > https://fedoraproject.org/wiki/Changes/Automatic_strict_inter-package_dependencies > > = Automatic strict inter-package dependencies = > > == Summary == > Implement feature in RPM which will enforce strict dependencies > between subpackages