Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: ffmpeg5-5.1.2
Date: Sat, 01 Jul 2023 04:09:39 +0200	[thread overview]
Message-ID: <20230701020939.Msc6ju52WEawwminEmTyHHjGiS5tOxKtuxMsbAJWXZk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42840@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2300 bytes --]

There's a closed pull request on the void-packages repository

New package: ffmpeg5-5.1.2
https://github.com/void-linux/void-packages/pull/42840

Description:
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**

#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)

#### Doesn't install with xi, help needed on that

After checking out [36315](https://github.com/void-linux/void-packages/pull/36315) and [41470](https://github.com/void-linux/void-packages/pull/41470) I've decided to create a separate ffmpeg5 package. There are a few good reasons for this :

- This is a clean and safe way to have ffmpeg5 in the source packages without breaking the other packages using the current ffmpeg ( 4.4.3 )

- I have problems with [36315](https://github.com/void-linux/void-packages/pull/36315), testing program compatibility by just compiling is not safe. ffmpeg 5 introduced major breaking changes, it should be the program creator who makes sure that the program works well with an updated dependency. With the ffmpeg5 package we can go through all packages one by one and and check if they are already using ffmpeg5 or not, and we can update them

- Since the ffmpeg project increases major version every year with breaking changes and the current version is 6.x, we will need a separate ffmpeg5 package anyway in the next year

- Since ffmpeg is a very important package used by lots of programs and major version changes very quickly it seems better to have versioned packages and the versionless just links to the latest or most stable one. We are already doing this with libvpx for example.

I went through ffmpeg 5's makefile and linked and enabled all the dependencies that are available for void and recent enough for ffmpeg 5.

It compiles fine on a clean void install and the binaries are there but for some reason 'xi ffmpeg5' is not working, the -devel package misses the compiled dependencies, I don't know how to tell xbps-src to install the libraries first, I would like to ask for help in this topic. I also couldn't test if the new shared objects break the packages linking to the old shared objects. 

      parent reply	other threads:[~2023-07-01  2:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-18 14:41 [PR PATCH] " milgra
2023-03-18 14:44 ` paper42
2023-03-18 14:45 ` paper42
2023-06-17  1:56 ` github-actions
2023-07-01  2:09 ` github-actions [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=20230701020939.Msc6ju52WEawwminEmTyHHjGiS5tOxKtuxMsbAJWXZk@z \
    --to=ml@inbox.vuxu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).