Dnia 2014-08-03, o godz. 12:11:48 Ulrich Mueller napisał(a): > >>>>> On Sun, 03 Aug 2014, Samuli Suominen wrote: > > > On 03/08/14 11:55, Ulrich Mueller wrote: > >> Do I get this right, you want the eselect module move files > >> installed by a package to another directory, effectively making > >> them orphans? > > > Of course it would require a pkg_postrm() phase that cleans up > > possible orphans > > Still, this would be very bad design. > > > But mgorny pointed out another solution in this thread, "Wouldn't it > > be better to generate exclude commands in bashrc?" > > And the answer to that would be "yes, of course" > > Can you remind me what was wrong with the current method, namely using > symlinks? The old method was pretty bad, and we can do it much better nowadays. IMO the best thing we could do is enabling by default and letting eselect disable stuff via adding (and enable via removing): complete -r foo to some well-defined file that gets sourced in bashrc. Then there's a matter of sourcing the file you need to source to enable completions at all. We could enable that unconditionally in bashrc, or use it for global completion switch in eselect. -- Best regards, Michał Górny