The current version of bitbake in portage is 0 which sounds weird to me. According to berlios, the latest version is clearly 1.2.1 so please put versioned ebuild into portage. Thanks...
bitbake is a live subversion ebuild, i.e. - uses files from bitbake svn trunk. No version bumps required here.
I thought svn/cvs ebuild are against gentoo policy. So, please see attached ebuild for version 1.2.1 and rename bitbake to bitbake-svn.
Created attachment 78558 [details] bitbake-1.2.1.ebuild
they are heavily discouraged bitbake generally doesnt do releases hence a live svn ebuild was added instead (in fact the ebuild was made almost a year before their first "release") i dont see much value in adding the 1.2.1 version, but i will rename the 0 to 9999 so people dont get confused
Well, why not add bitbake-1.2.1 and bitbake-svn-0? I'm using 1.2.1 without problems. I mean, you'll get problems when you provide only svn version since when someone downloads it when it's in broken state, gentoo gets flamed. :-( Providing ebuild for release version is a sure thing (in means of working state). Anyway, I can try to write to bitbake developers and ask them to make a release...
Created attachment 78575 [details] bitbake-1.3.2.ebuild This is an ebuild for version 1.3.2 which is the latest stable. Very close to what you get when you pull it from svn.
I've had a conversation with the devs and they said there will be more releases coming so it imho makes sense to keep ebuilds for released versions...
having sep packages for livesvn and releases is a waste of space moved 0 to 9999, then cleaned up and added 1.3.2 to portage
