-
Notifications
You must be signed in to change notification settings - Fork 17
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
Draft Gentoo ebuild #2
Comments
Updated orbital ebuild, with the Oxygen Qt theme as a runtime dependency:
|
I looked at the flags you added and I am trying to get the ebuild to set them. When I added them to the ebuild it runs cmake with these arguments: '-Dalsa=ON' and '-Dsolid=ON', when they are enabled (and OFF when disabled). Is this the correct way to set those flags? |
no, it's -Duse_alsa/solid=0 or 1 |
Okay, the ebuild below will use, e.g. '-Duse_alsa=ON' which looks like a synonym for '-Duse_alsa=1'. The documentation I was using for this is here: I also updated the license string. I will do another test build of this and then submit it, unless there are more changes that need to be made.
|
From my nonexistent knoweledge of ebuilds and gentoo these look good to me :). |
Okay. I am basically waiting on this: Also, people might have a problem with the ebuilds if they have to upgrade GCC to fix the bug that makes the Nuclear compilation fail. I can list the upgraded GCC as a dependency, but it can be installed alongside the previous version and I don't know how to tell it to select the newer version automatically. And the ebuild might be postponed for addition into the distributed set of ebuilds (portage) until the new version of GCC is marked as the stable one. This is my first ebuild, so I don't really know what Gentoo's policies are. If there is an easy workaround that either you could do in the code, or I could do in the ebuild, it might improve the odds of getting it into portage. I have been tweaking the required dependencies. I looked through the code and I think I got all of them, but maybe you could double check? It would also be helpful to know what the minimum required versions are (I just guessed). Nuclear dependencies (DEPEND is build dependencies, RDEPEND is runtime dependencies):
Orbital dependencies:
|
The mixer and device explorer are still being built when the flag to turn them off is passed to cmake, they just complain on the log that their backends are missing. Maybe it would be better to remove the applets completely with the flags turned off, and then handle their absence in the UI/config files? I am having problems building Solid on Gentoo. I thought I had it working before but it broke again. The ebuild for it uses the bleeding edge development version and it hasn't been added to portage yet, so I have turned the "kde-solid" flag off by default. |
After looking at the source code, it looks like dbus can be dropped entirely if the user is going to be using the CLI backend. I need to figure out the exact list of dependencies for the logout/shutdown so that I can add a USE flag for that, and if that flag and kde-solid are disabled, then a USE flag for dbus could be disabled. Also, is linguist-tools needed if translations are not used? Would the untranslated language then be English, or would it be Italian? |
That's right, dbus is used only for logind and solid indirectly. Using -Duse_logind=OFF and -Duse_solid=OFF should remove any dependency on it.
No, but there is no way to disable the translations for now. The untranslated language is English. |
Here are the ebuilds that I used to build Nuclear and Orbital. I plan to submit them once I finish working out the bugs:
dev-libs/nuclear/nuclear-9999.ebuild:
app-misc/orbital/orbital-9999.ebuild:
The text was updated successfully, but these errors were encountered: