I changed the fpc.ebuild to use the rpm.eclass instead of rpm2tgz in the ebuild. Further I made an ebuild for the latest beta (1.9.4 aka 2.0.0-Beta3) which is used by my lazarus.ebuild (#33019). Both patches are diffs against the ebuild which is in portage now Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 35112 [details, diff] fpc-1.0.10.ebuild.patch
Created attachment 35113 [details, diff] fpc-1.9.4.ebuild.patch
Chris is now maintaining this package.
Hello, I tried to apply the fpc-1.9.4.ebuild.patch to the current fpc-1.0.10.ebuild, but this failed. I tried to apply the fpc-1.0.10.ebuild.patch first, but this failed, too. Could you please attach a complete ebuild for fpc-1.9.4 instead of a patch? Regards: ufechner
Created attachment 38966 [details] fpc-1.9.4.ebuild
Removed the blocker for fpc-source.. bad boy. Basically, if someone builds fpc-source, then fpc, then removes fpc-source, they both install the same files, so fpc is going to be broken. Removed the src_compile verboseness, don't need that. Other than that, good job.
>Removed the blocker for fpc-source.. Well I did not remove the blocker actually. In the time of writing this (July) there was simply no blocker in the ebuild as you can see in the patches. After comment #4 I simply took my version from the Portage-Overlay. My fault, I should have rechecked the original ebuild for changes in this time. >Removed the src_compile verboseness, don't need that. Thanks, I will know that for the next time.
started a fpc cvs ebuild at bug # 79985
