Edited the note at the end to avoid false positive bug reports resulting of users who missed to update the config. Reproducible: Always Steps to Reproduce:
Created attachment 57018 [details] fpc-2.0.0_rc2.ebuild
George, do you care about ChrisWhite's "dev-lang/fpc*" stuff? I'd take it. My approach would be to kill everything beside dev-lang/fpc, we have too much unmaintained packages in the tree.
How about slowing down a bit. I told you like 3 times in other bugs concerning fpc and lazarus that i'll supply updates for the next 2 years since i'll use those tools for that time. I'd have liked it if you asked me about that before talking about deleting all this...
Daniel: You didn't told me anything. I'm not subscribed to the lang-misc alias. The point is that we need devs, who care for ebuilds. Even if you do the ebuilds, a dev has to care for it. Also I don't see a point in having multiple ebuilds for fpc - one should suffice. And you shouldn't bother, since you create them for yourself anyways.
I'm sorry - i thought you were on that alias. Anyway there wouldn't be far more to do than proofreading and commiting into unstable... Things that I would - if i were you - keep in portage are fpc fpc-ide fpc-source lazarus since they are kind of popular i guess (yet got 3 mails concerning the new lazarus ebuild i submitted...) further on i also considered writing a fpc-doc but it is not that important since all the docs are available online (similar to gcc's) The other ebuilds (and other versions like the most recent of those i just named) are outdated and not important at all seen from my point of view (i also consider the demand on them, of course, which is really low i guess.) besides this - of course i could write them for myself, but because i know that others looked forward to them and use them i would keep those ebuilds in portage, as i said before - also, if i write one of those ebuilds i always like to share them... That's it.
FPC 2.0 was released, anybody write the ebuild for it?
Thanks for the hint. I'll try to update the ebuild quickly (That'll make the version attached here unneeded, I'll incorporate the changes into the release of v2)
Closing this bug, since it is irrelevant now. Opening a new one for 2.0 release which will include the 2.0 ebuild for compiler and sources.