Created attachment 371974 [details] Patched version of the latest vim ebuild The current ebuild has two feature-set options: 'tiny' and 'huge'. This update enables selection of any particular feature sets, while maintaining backward compatibility with the existing ebuild (specifically, minimal always means 'tiny' and no specification always means 'huge'). This implements the feature set selection via USE_EXPAND vim_features (which corresponds to the --with-features configure switch).
Created attachment 371976 [details] Patched version of the latest vim metadata.xml
Created attachment 371980 [details] USE_EXPAND description file
Please attach patches for changed files, especially ebuilds. With that said, I'm not convinced we need to support this level of granularity.
Created attachment 371996 [details, diff] patch for ebuild
Created attachment 371998 [details, diff] patch for metadata.xml
The request is to accommodate an issue from CoreOS dev wherein there is a desire to have the small feature-set (which contains, for instance, visual mode) in order to keep the installed size down. Rather than maintain a separate ebuild, it seemed more effective to simply allow users to explicitly declare their desired feature-set as a USE flag.
That was poorly-worded, sorry. In short, we're looking for a way to select a feature-set between 'tiny' (which is configured with the 'minimal' USE flag) and 'huge' (which is configured otherwise). In this case, 'small' was chosen as optimal, but rather than adding random basic use flags, it makes more sense to simply expose the option directly.
Created attachment 372000 [details, diff] patch for ebuild Fix reference: large -> big
Created attachment 372002 [details, diff] patch for metadata.xml fix references large -> big
After much debate on IRC, we decided not to implement this feature. If you do want to compile vim with a special set of features, go check out the EXTRA_ECONF variable and make sure to pass it to emerge at compile-time.
