harder and harder to avoid pkg

[Vlad K.]

On 2016-10-12 10:27, Julian Elischer wrote:
> what I really need is a RUNTIME option that produces a package with
> only those files needed to satisfy external run-time depdencies, or
> the actual demands of the user itself. However since those files are

Right. But then the question is how do you define what is minimum 
required code to satisfy external run time deps? Can the framework 
assume it by path, or should the maintainers define it through options?

IMHO if the latter, then my suggestion is not to define any roles 
("runtime") but define groups of files that can then be included in 
whatever role. Eg, all include/... files be switched with HEADERS 
option. Many ports already do DOCS, MANPAGES, EXAMPLES. So that's a set 
criteria one can base -runtime variant upon:

OPTIONS_UNSET= HEADERS DOCS MANPAGES EXAMPLES


-- 

Vlad K.