-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
media-plugins/distrho-ports: add version 2021-03-15 #550
base: master
Are you sure you want to change the base?
Conversation
5c2761f
to
068d26a
Compare
Seems like the CI pipeline is unable to build the package due to missing dependencies (fftw3f): Could you please have a look at the dependencies? |
I have added a commit which takes care of the additional dependency. Is this conditional syntax acceptable in live ebuild files? If not, my plan would be to copy the ebuild to 20210115 (which does not yet depend on FFTW) and make the change to the live ebuild (unconditionally) afterwards. Does that sound better? |
I'm not really a fan of symlinked ebuilds and putting if blocks in the live ebuild for every extra detail just makes the ebuild overly complicated. Hence, I'd prefer if you don't use symlinks and instead copy the files and add the dependency only in the live ebuild. |
Since the addition of the vitalium plugins on 2021-03-01, distrho-ports has been requiring FFTW as a dependency. Get rid of ebuild symlinks, split the ebuilds between release (YYYYMMDD) and live (99999999) ebuilds, and add the FFTW dependency where required.
Allow building media-plugins/distrho-ports-20210115 with GCC 12 or later.
7296345
to
11c0523
Compare
I agree. This pull request now removes symlinks and provides three separate ebuilds: the last two released versions of DISTRHO-ports and the live ebuild. It also adds a patch for version 2021-01-15 because that version did not build with GCC 12 or 13 (have tried GCC versions 11, 12, and 13). If you decide to rather drop the ebuild for DISTRHO-ports version 2021-01-15, that’s fine for me, too. In this case, the patch can be removed as well as it is not required for later versions. |
Nice job! Unfortunately, the CI pipeline fails:
Again, this looks like something is wrong with the dependencies. Maybe there's some new configurable options which can be sensibly translated to USE flags? You might wanna try using dev-util/ebuildtester to test the ebuild in a clean environment (only if you have Docker, though). So, in general I'm okay with this PR. It's just the missing dependencies or configure options that need fixing. |
Thanks for the hint about I haven’t been able to reproduce the issue. When trying the ebuilds with
This works as well. The (slightly extended) part of the build log that corresponds to the part which failed on CircleCI is:
I have also tried That means either something is very wrong on my end or in the CircleCI pipeline (or both, or something completely different is going on). As far as I understand it, a cache |
Sorry, but I'm currently a very busy. I can't promise that I'll have a look at this until october. I hope that's okay! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few minor questions, but looks fine overall.
# Copyright 1999-2023 Gentoo Authors | ||
# Distributed under the terms of the GNU General Public License v2 | ||
|
||
EAPI=7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are on EAPI=8 now. Please consider bumping the EAPI.
@@ -1,22 +1,14 @@ | |||
# Copyright 1999-2021 Gentoo Authors | |||
# Copyright 1999-2023 Gentoo Authors | |||
# Distributed under the terms of the GNU General Public License v2 | |||
|
|||
EAPI=7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As before, please consider an EAPI bump.
if [[ ${PV} == *9999 ]]; then | ||
inherit git-r3 | ||
KEYWORDS="" | ||
else | ||
MY_PN="${PV:0:4}-${PV:4:2}-${PV:6:2}" | ||
SRC_URI="https://github.com/DISTRHO/DISTRHO-Ports/archive/${MY_PN}.tar.gz -> ${P}.tar.gz" | ||
KEYWORDS="~amd64" | ||
S="${WORKDIR}/DISTRHO-Ports-${MY_PN}" | ||
fi | ||
KEYWORDS="" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason to remove the if
block? Keeping the if
block would allow us to only maintain the live ebuild and copy it over to new versioned ebuilds upon new releases.
Not the most sophisticated piece of work ever accomplished, but works for me.
Fixes #455.