I needed it for OE building (OpenEmbedded), so I made one. Not sure how to go about submitting this, but I read somewhere this was how. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 66611 [details] tar of ebuild, digest and patches Ebuild, patches and digest for source code. Test please.
Comment on attachment 66611 [details] tar of ebuild, digest and patches untar to /usr/local/portage/dev-embedded, (dev-embedded/bitbake)
This is my first ebuild, so there are probably problems/mistakes. I will fix as needed. Only gotcha on this ebuild is that user must set env variable BBPATH to point to system bitbake configuration file (installs to /usr/share/bitbake/conf/bitbake.conf) so BBPATH=/usr/share/bitbake AND User must also add their custom configured "local" configuration file path, which is wildly dependent where they put their configuration info for say OpenEmbedded.
This is my first ebuild, so please have patience... There may be problems. I know for sure that one thing missing is that ENV variable BBPATH must be set to location of several things, some of which do not get installed with bitbake, but must be added by user manually. I'm thinking to add BBPATH to /etc/profile, but since it needs to be appended to by user maybe this isn't the right place.
Heh, the ebuild in portage fetches the files from SVN, so it's hardly old. :-) Do you still want this in portage?
Um.. yeah it kindof does I guess. You just have to re-emerge to get the new version (since portage doesn't consider the -0 to be an new version even if the svn version has changed). Thats why I bothered with this in the first place, I was stuck at version 0.X and didn't see an ebuild for anything newer, and portage wouldn't tell me I could upgrade to a newer version. Kindof a gotcha...
I'm gonna close this because my solution is silly. Never mind.
