Skip to content
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

Feature Request: Compilation options #49

Closed
anders-larsson opened this issue Oct 11, 2013 · 5 comments
Closed

Feature Request: Compilation options #49

anders-larsson opened this issue Oct 11, 2013 · 5 comments

Comments

@anders-larsson
Copy link

It would be great if more options was added to the ./configure script to disable functions which not everyone wants.
Examples:

  • Disable/Enable pulseaudio (libraries required to compile but not really necessary to record sound in ssr I guess). Correct me if I'm wrong though

PS: I'm maintaining a Gentoo ebuild for ssr. It can be found here https://github.com/anders-larsson/gentoo-overlay/

@MaartenBaert
Copy link
Owner

I will add a configure option, but are you sure that you want to disable it completely? libpulse is already a dependency of many other project and it's not very large by itself: it doesn't pull in PulseAudio on most distros AFAIK, is Gentoo different?

Your package (ebuild?) would be useful for other users as well, will they still be able to enable PulseAudio?

@anders-larsson
Copy link
Author

There's no package available only to include the libs in Gentoo. Pulseaudio libs is provided by media-sound/pulseaudio which provides the whole suite (depending on USE-flags). Some just don't like Pulseaudio that's all I know.

I'm using Pulseaudio myself and will continue to do so. Gentoo allows you to use USE-flags to decide what functionality you want in your package. So pulseaudio will be included as a useflag.

An ebuild describes the required/optional dependencies and how to build the package successfully.

@anders-larsson
Copy link
Author

I've updated the ebuild to support disabling/enabling pulseaudio and a few other options.

Thanks for providing us with a good screen recording program. Would help contribute if I had the knowledge.

@MaartenBaert
Copy link
Owner

You're welcome :).

I would like to add your overlay (if that's what it's called in Gentoo) to my website, is that okay? Should I just link to the github page and assume that Gentoo users know what to do with it? I have no experience with Gentoo.

I saw that your package is called 'ssr', I think it would be better to call it 'simplescreenrecorder' for consistency with the program name (/usr/bin/simplescreenrecorder) and the packages for Ubuntu and Arch. It would also reduce the risk of naming conflicts.

Also:

elog "To build these add 'media-video/ssr abi_x86' to package.use"

Shouldn't that be abi_x86_32?

@anders-larsson
Copy link
Author

I would like to add your overlay (if that's what it's called in Gentoo) to my website, is that okay? Should I just link to the github page and assume that Gentoo users know what to do with it? I have no experience with Gentoo.

It sounds great. Not worth keeping the ebuild to myself. I guess it should be enough to just add the overlay to your site. I might contact Gentoo to get the overlay listed in layman. It makes it even easier since then someone would just need to do "layman -a repository; emerge simplescreenrecorder" (they would probably want to set USE flags though) and every should be up and running.

I saw that your package is called 'ssr', I think it would be better to call it 'simplescreenrecorder' for consistency with the program name (/usr/bin/simplescreenrecorder) and the packages for Ubuntu and Arch. It would also reduce the risk of naming conflicts.

I've renamed the ebuilds/package to simplescreenrecorder. Agreed. The name 'ssr' could easily lead to naming conflicts.

Also:
elog "To build these add 'media-video/ssr abi_x86' to package.use"
Shouldn't that be abi_x86_32?

That's changed now. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants