[Solved] Ebuild files for script-based utilities

[lars_the_bear]

Hi folks

Is there a nice way to write a .ebuild file for a utility that consists of nothing but scripts? There's a Makefile, but only 'make install' does anything, because there's nothing to build. I'm fairly sure these utilities could be treated like C programs, but is there an official, nicer way? I guess I could just provide empty implementations of `src_compile()` etc.

BR, Lars.

[logrusx]

[RumpletonBongworth]

An implementation of src_compile that does nothing would save a minute amount of overhead. You can do what whatever you want in the src_install phase (exeinto, doexe etc).

EDIT: I just realised that you mentioned that there is already a Makefile. In that case, and as logrusx stated, you shouldn't have to do anything in particular.

[eschwartz]

If the default Makefile target does something incompatible with src_compile, such as attempting to install to $(DESTDIR)/usr/bin, then you do indeed need to override src_compile.

Or make the default Makefile target be a no-op target, which is a good idea anyway. It's not generally expected that running `make` would install the software.

Perhaps this Makefile is already doing the right thing and the default target is a no-op.

(If there is *no* Makefile, then you don't need to do anything since it will only try to execute a Makefile if a Makefile exists.)

[lars_the_bear]