On 30/03/14 11:45, [email protected] wrote: > Hello *, > > Claus-Justus Heine <[email protected]> has recently > contributed an ebuild for the latest version of geomview plus 8 ebuilds > for additional "emodules" which extend the functionality of geomview. > They are rather small packages depending on geomview and sometimes on > something else. I have committed the bumped geomview (after the > necessary changes). Hi, and thanks for your contributions.
> > What would be the best way to deal with these emodules? > 1. Commit 8 new packages I would go for this. In case of a change for any of the modules (bugfix or so) you have the minimal rebuild for the user. > 2. Add 8 USE flags to geomview, and buildinstall these emodules > depending on the flags You should avoid adding USE for the modules, as a change in the USE, which should only pull in the new module from the separate package, will also trigger a rebuilt of the whole application. Best solution here is to take the middle. Add a USE minimal which is default "+minimal" and add depend !minimal? ( .... ). That way you can depend on all modules or none. And add a postinst message that tells the user about the modules and which can be installed. take a look at media-sound/guayadeque for an example. Justin
signature.asc
Description: OpenPGP digital signature
