On Thursday 14 January 2016 14:01:30 Slávek Banko
wrote:
On Thursday 14 of January 2016 14:24:42 Michele
Calgaro wrote:
On 01/14/2016 04:53 AM, Greg Madden wrote:
It is not possible to give tdesudo as a necessary
dependency for all.
Would
> it be possible to consider only for the meta package on Ubuntu,
> where sudo is used by default.
I think it would be better to NOT add a dependency.
Perhaps we can add a "recommends" for tdesudo to tdebase or something
similar. Then it is up to the user to decide whether to install tdesudo
or not. Just my 2 cents.
Michele
tdesudo-trinity is already as 'recommends' for metapackage
kubuntu-desktop-trinity == for ordinary Ubuntu users.
How can remove these, to me, undesirable security risks, from 3.5.13.2? I
have tried, but they are so tied in with things dependant on them that
simply removing is not an option.
The following packages will be REMOVED:
sudo{p} sudo-trinity{p}
0 packages upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 1,919 kB will be freed.
The following packages have unmet dependencies:
kde-core-trinity : Depends: sudo-trinity but it is not going to be
installed. kdelibs4c2a-trinity : Depends: sudo but it is not going to be
installed. gksu : Depends: sudo but it is not going to be installed.
The following actions will resolve these dependencies:
aptitude then suggests removing 304 packages.
I said "q".
But is it possible to get the wretched things off my and my clients'
machines less drastically??
And please, please don't force it on us any more. We don't all like it.
Choice, please, choice. Learn to use apt and its offspring and
descendants, Gene.
Lisi
Lisi
Yes, just a few days ago, I also researched why kdelibs / tdelibs have sudo
stated as 'depends' == is always installed and can not be uninstalled. And I
see no compelling reason for this. Therefore, I propose to remove this
dependency. Does anyone have a convincing argument against this?
--
Slávek