"You started posting one message a day (or more) on the tone "why this is not as I want it? ...you should include this because etc. etc. add_my_wish here" of course in certain cases you did provided a valuable feedback, thank you."
"Eventually you posted your very last innuendo saying that in fact you are pretty happy and used with redhat (and there is nothing wrong with that) and your interest in collegelinux was marginal."
Fair enough. I was being a jerk vacillating between geek fatigue and curiosity. The Red Hat stuff was mostly the geek fatigue talking, which doesn't justify it, of course. My mouth runneth over. Mea culpa.
That said, the 'kdelinks' package really does need to go. A .desktop file is supposed to be bundled with the application package, so that menu entries appear and disappear as apps are installed and uninstalled. That's why each menu entry is stored in a separate file instead of having the menu entries all in one config file as most plain window managers do.
"You started posting one message a day (or more) on the tone "why this is not as I want it? ...you should include this because etc. etc. add_my_wish here" of course in certain cases you did provided a valuable feedback, thank you."
"Eventually you posted your very last innuendo saying that in fact you are pretty happy and used with redhat (and there is nothing wrong with that) and your interest in collegelinux was marginal."
Fair enough. I was being a jerk vacillating between geek fatigue and curiosity. The Red Hat stuff was mostly the geek fatigue talking, which doesn't justify it, of course. My mouth runneth over. Mea culpa.
That said, the 'kdelinks' package really does need to go. A .desktop file is supposed to be bundled with the application package, so that menu entries appear and disappear as apps are installed and uninstalled. That's why each menu entry is stored in a separate file instead of having the menu entries all in one config file as most plain window managers do.