04a9309f33
If fpdb is installed using an ebuild for the very first time then fperms mysteriously fails marking the *.pyw files as executables. During a second install from the ebuild fperms was working which is more mysterious. I have found notices about this behaviour of fperms but couldn't find a proper solution. However simply replacing fperms with chmod just does the work done. Signed-off-by: steffen123 <steffen@schaumburger.info> |
||
---|---|---|
.. | ||
current_stable.ebuild | ||
current_testing.ebuild | ||
fpdb-9999.ebuild | ||
readme.txt |
If you want to run a stable version please use current_stable.ebuild If you want to run a testing version please use current_testing.ebuild To use the ebuild please simply copy it into your local portage tree and rename it to fpdb-version.ebuild, for example fpdb-0.20.1.ebuild or fpdb-0.20.902.ebuild. Here's a little howto on how to utilise 3rd party ebuilds such as this one: http://www.gentoo-wiki.info/HOWTO_Installing_3rd_Party_Ebuilds