Skip to content

Conversation

@prototype99
Copy link

You will need to give this its own branch most likely. The aur package has started failing because the libirecovery aur package that is available is too new and causes version 1.0.0 to fail. Whilst I understand that a new release is in development and you may not wish to make a new release yet, I think at the very least this is a good compromise, it should work with old libirecovery versions, just like the current version, as well as newer versions of libirecovery. This should help prevent complaints that the current version is 'broken' and 'doesn't build' as more distros start to use the newer libirecovery versions, without harming other distros that choose to keep using older libirecovery versions

Adapts to API changes in libirecovery where the irecv_init() function may no longer be available or required.

Introduces a configure check to determine the presence of irecv_init(). IRECV_MAYBE_INIT(), is then used to conditionally call irecv_init() only if it exists, preventing build failures and ensuring proper behaviour across different versions of libirecovery.

Adapts to API changes in libirecovery where the `irecv_init()` function may no longer be available or required.

Introduces a configure check to determine the presence of `irecv_init()`. `IRECV_MAYBE_INIT()`, is then used to conditionally call `irecv_init()` only if it exists, preventing build failures and ensuring proper behaviour across different versions of libirecovery.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant