Buildtool is a portable build infrastructure that can be used in the development
of any kind of program. Buildtool is like an improved auto tools package.
I suggest dev-util category.
I think it is necessary to include the *new* bsd license to the portage tree.
Created attachment 14061 [details]
Created attachment 16459 [details]
Added DEPEND= & IUSE= variables for correctness.
Created attachment 16954 [details]
"emake" should not be used in this ebuild, changed to "make", now it works
Version bump. Ignore meee !
Created attachment 17131 [details]
From the homepage:
But I must admit it. The code is, in its actual form, dead :-( It's unmanageable
(shell scripting doesn't scale, you know) and breaks in many, many places. Just
consider the following facts:
* Detection of C++ features from bt_config fails in many cases.
* bt_logic's behavior is less than acceptable, and adding functionality to
it is a PITA.
* Several modules haven't been modified across versions, so they don't work
properly. For example, bt_lint is almost useless.
* Shared library handling is broken in many systems, and fixing it could be
* The code exposes internals too much, specially in environmental variables
and C/C++ defines. But cleaning that up is also complex due to the nature of
* I was suggested recently to make bt_dist only include in tarballs what was
really needed, and not everything (just like GNU Automake's make dist does. I
like the suggestion, but implementing correctly is impossible due to the current