On 9 August 2014 01:12, Igor <lanthrus...@gmail.com> wrote: > Most of the maintainers just depend on new > packages not knowing if it's necessary or not resulting in a really HUGE > update that in the absolute majority of cases destabilize GENTOO making it > not operational and WORSE than it was before. You then STABILIZE it again > spending hours and then the story repeats itself.
Some of your assumptions seem misguided. Some cases, dependencies are forward specifications from upstream telling us what their software needs to function properly. Failing to meet that requirement could void our support warranty from upstream. Likewise, using 'nodeps' voids your support warranty from gentoo. And just because "it works for me" that doesn't mean its not broken, it just means you've not encountered the broken scenario that the dependencies exist to guard against. Very often upstream will discover a case where X doesn't work in 10% of the problem space. There's no way to communicate to a user what you will and will not do with the software, so its impossible to know what flaws you will and won't encounter, so the dependencies thus declare a minimum for expected working behaviour for *all* a software's functionality, not just your user-specific subset. If you wish to override that decision, you may, but your self-supporting from that point on. TL;DR = just because it works /for you/, doesn't mean it /isn't broken/ and doesn't mean the minimum declaration is "unnecessary" for all users. -- Kent *KENTNL* - https://metacpan.org/author/KENTNL
