Re: [gentoo-dev] vim and gvim package split

[Kent Fredric <kentfredric@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]

On 1 November 2013 11:02, Alessandro DE LAURENZIS <just22.adl@gmail.com>wrote:

>
> In case of vim-core/vim/gvim (and vim-qt?), I cannot understand
> the reason... Are still there advantages in doing so?


Useflags have their perks for giving variations on behaviour, but having 3
effective packages in one, governed by useflags, means you'll have 3 much
more tightly coupled packages, and the code will be much messier with
useflag conditionals to pull dependencies.

If you imagine useflags like "if" statements, and ebuilds like independent
classes where "dependencies" are a kind of inheritance, you may find
theres' reasonable benefits for the maintenance side

e.g.: people checking reverse deps for QT don't have to worry about changes
in QT breaking vim and gvim because those packages are independent of QT
interaction

Fixes that need to go in to make building vs QT mean only the qvim ebuild
gets updated and the rest are fine as-is.

The only real downside is if you're building all 3 {q,g,}vim there's a
little compile time overhead as a result ( Though I'm not sure what the
difference is in real terms )

But by having them seperate, we enjoy a more robust installation,
especially for people who only want one of the 3, then they're not
needlessly burdened by logic to handle things they're not using, which
could break.

Not to mention you have to deal with overheads introduced by having to work
out the equivalent of all three of the above having vastly different
useflags and making useflags conditional upon each other as a result to
codify the same behaviour, again, further raising the odds that a
situtation will arise where things break and the dependencies/use flags
are  a mess.

-- 
Kent

[-- Attachment #2: Type: text/html, Size: 2427 bytes --]