New ebuild for gentoo

[GoogleCodeExporter]

What steps will reproduce the problem?
1. the ebuild of the repo is not updated is pointing to svn repository instead 
of git repository.

I have updated and tested ebuild for gentoo. It is pointing to git repository 
and it's working. I have attached the ebuild with one extra file. This file is 
necesary to compile in gentoo. I would like 
this file update the ebuild of the git repository.

Original issue reported on code.google.com by granados...@gmail.com on 2 Apr 2011 at 6:15

Attachments:

• osd-lyrics.tar.gz

[GoogleCodeExporter]

Thanks for your ebuild.

I think the chardetect patch is no longer needed.
IMHO, the develop branch is more suitable for this 9999 ebuild.
For end-users, clone from http repository instead of https is enough.

What's your opinion?

Original comment by tigerso...@gmail.com on 5 May 2011 at 7:03

[GoogleCodeExporter]

You are ok the chardetect patch is no longer needed. 

I have changed url from https to http.

About the 9999 ebuild, I have changed to develop branch.

I have implemented new ebuild for stable version. I link the ebuild to master 
and a concrete commit. If you generated a new version, you have to change name 
of ebuild to new version and set the variable EGIT_COMMIT to new commit value 
matching this version.

Thanks, for your job in the project and your attention.

Original comment by granados...@gmail.com on 9 May 2011 at 11:47

Attachments:

• osd-lyrics-4.3.ebuild
• osd-lyrics-9999.ebuild