I have attached an ebuild for Logo++, which is a Logo-like interpreter. The homepage is: http://clpp.sourceforge.net/ I suggest that it be placed in dev-lang/logo++. There are no dependencies of which I am aware. Cheers, Josh
Created attachment 22304 [details] dev-lang/logo++-0.0.1b.ebuild (New Package)
Created attachment 22325 [details] Add Logo++ dependency Logo++ depends on fltk 1.0.11 (it won't work with newer versions) and on the flex library (needs -lfl option for linking). I am new to ebuild files, but I would modify it that way : DEPEND="=x11-libs/fltk-1.0.11 sys-devel=flex" is it ok ? --chaker
Created attachment 22345 [details] dev-lang/logo++-0.0.1b-r2.ebuild (Update) I added the Flex and fltk dependencies, as the author suggested. However, I compiled and ran Logo++ without fltk, so is it really a dependency? The dependencies section now looks like this: DEPEND="sys-devel/flex =x11-libs/fltk-1.0.11*" The star is necessary, as the fltk-1.0.11 ebuild in Portage is -r3, so =x11-libs/fltk-1.0.11 would not work. That seems like a bit of a hack, but...
Chaker, Please Edit your attachment ("Add Logo++ dependency") and mark it as obsolete. My -r2 ebuild handles the dependencies you pointed out.
Taking this bug. The project looks pretty stalled, but no reason the release should not be in Portage, as SourceForge is hosting it.
Argh! Why does "Accept this Bug" not reassign it to me? Why must I go through two steps!?
This ebuild is ancient, the project is not being developed, and it does not compile. No need for this in Portage, methinks.