mbox series

[bug#76339,core-updates-team,0/4] Update libde265 and remove dependency on qtbase-5.

Message ID cover.1739717336.git.monego@posteo.net
Headers
Series Update libde265 and remove dependency on qtbase-5. |

Message

Vinicius Monego Feb. 16, 2025, 2:56 p.m. UTC 
  This series updates and removes the unused inputs of qtbase-5 on libde265. Removing this input would clear a transitive dependency of 400+ packages on qtbase-5, so I am sending this to core-updates-team but it could be pushed to master if wanted.

As said in the commit message, qtbase-5 is a dependency for 'sherlock265', a h265 developer tool. It was not being built already because it depends on either libvideogfx or
libswscale, and is not useful for dependent packages which only link the library.

Vinicius Monego (4):
  gnu: libde265: Remove dependency on qtbase-5.
  libde265: Remove package labels.
  gnu: libde265: Update to 1.0.15.
  gnu: libde265: Use G-Expressions.

 gnu/packages/video.scm | 20 ++++++--------------
 1 file changed, 6 insertions(+), 14 deletions(-)


base-commit: b4dc8eb4adff9d824ff7df704e134964b3b47396

Comments

Nicolas Graves Feb. 16, 2025, 4:21 p.m. UTC | #1 
On 2025-02-16 14:56, Vinicius Monego wrote:

> This series updates and removes the unused inputs of qtbase-5 on
> libde265. Removing this input would clear a transitive dependency of
> 400+ packages on qtbase-5, so I am sending this to core-updates-team
> but it could be pushed to master if wanted.

Hi Vinicius,

I made a similar commit in 74517 that should be (haven't checked)
applied in the gnome-team branch.
Leo Famulari Feb. 17, 2025, 11:12 p.m. UTC | #2 
On Sun, Feb 16, 2025 at 05:21:21PM +0100, Nicolas Graves via Guix-patches via wrote:
> On 2025-02-16 14:56, Vinicius Monego wrote:
> 
> > This series updates and removes the unused inputs of qtbase-5 on
> > libde265. Removing this input would clear a transitive dependency of
> > 400+ packages on qtbase-5, so I am sending this to core-updates-team
> > but it could be pushed to master if wanted.
> 
> Hi Vinicius,
> 
> I made a similar commit in 74517 that should be (haven't checked)
> applied in the gnome-team branch.

Okay Nicolas, gnome-team sounds fine to me.

Vinicius, we are no longer using a core-updates branch, and I don't
there is no core-updates-team. See here for the new workflow:

https://guix.gnu.org/manual/devel/en/html_node/Managing-Patches-and-Branches.html

There is a 'core-packages' team, but that's for packages that are truly
at the root of the dependency graph:

https://git.savannah.gnu.org/cgit/guix.git/tree/etc/teams.scm?id=e4b54095cbe377ea526719b3d5dcc619e111aa2a#n490

Maybe we should make a 'media' team that would handle things like video
codecs, as they tend to trigger a lot of rebuilds these days, and they
don't really fit anywhere else.
Maxim Cournoyer Feb. 18, 2025, 6:53 a.m. UTC | #3 
Hi Leo,

Leo Famulari <leo@famulari.name> writes:

> On Sun, Feb 16, 2025 at 05:21:21PM +0100, Nicolas Graves via Guix-patches via wrote:
>> On 2025-02-16 14:56, Vinicius Monego wrote:
>> 
>> > This series updates and removes the unused inputs of qtbase-5 on
>> > libde265. Removing this input would clear a transitive dependency of
>> > 400+ packages on qtbase-5, so I am sending this to core-updates-team
>> > but it could be pushed to master if wanted.
>> 
>> Hi Vinicius,
>> 
>> I made a similar commit in 74517 that should be (haven't checked)
>> applied in the gnome-team branch.
>
> Okay Nicolas, gnome-team sounds fine to me.
>
> Vinicius, we are no longer using a core-updates branch, and I don't
> there is no core-updates-team. See here for the new workflow:
>
> https://guix.gnu.org/manual/devel/en/html_node/Managing-Patches-and-Branches.html
>
> There is a 'core-packages' team, but that's for packages that are truly
> at the root of the dependency graph:
>
> https://git.savannah.gnu.org/cgit/guix.git/tree/etc/teams.scm?id=e4b54095cbe377ea526719b3d5dcc619e111aa2a#n490
>
> Maybe we should make a 'media' team that would handle things like video
> codecs, as they tend to trigger a lot of rebuilds these days, and they
> don't really fit anywhere else.

I think Nicolas knows that given their subject prefix is
'core-updates-TEAM', and using it simply as a hint that this causes a
large rebuild.  We don't have this documented yet, but it makes sense to
communicate this information to help avoiding inadvertently merging
large changes to the main branch.
Leo Famulari Feb. 18, 2025, 7:05 p.m. UTC | #4 
On Tue, Feb 18, 2025, at 01:53, Maxim Cournoyer wrote:
> Leo Famulari <leo@famulari.name> writes:
>> Vinicius, we are no longer using a core-updates branch, and I don't
>> there is no core-updates-team. See here for the new workflow:
> I think Nicolas knows that given their subject prefix is
> 'core-updates-TEAM', and using it simply as a hint that this causes a
> large rebuild.  We don't have this documented yet, but it makes sense to
> communicate this information to help avoiding inadvertently merging
> large changes to the main branch.

I had meant to write "I don't think there is a core-updates-team".

Sorry for the confusion.