[SOLVED] KDE now depending on mono (via libgpod)?

[nindnarne]

Apologies if I posted this one in the wrong thread....

I just did the big upgrade.

I saw one of the new dependencies, which to my shock was Mono. I tracked the dependency down to libgpod and lib4gpod, ie the stuff you need to access Ipods etc. I tried removing those packages but it turns out that Kipi, Digikam, Amarok and other KDE apps depend on those two packages.

In effect, the KDE packages from Pclos now depend on Mono/.Net....?

I fully understand that the developers do as they want to do, but would it be possible to have KDE and associated apps without having to depend on Mono/.Net/Microsoft....?

Thanks for your understanding ;-)

[Padma]

I just removed amarok and digikam from my system (by removing "task-kde4-extras).  I refuse to install mono on my system.  Imagine my shock when I saw these had mono as a dependency!

[moniac]

I just removed amarok and digikam from my system (by removing "task-kde4-extras).  I refuse to install mono on my system.  Imagine my shock when I saw these had mono as a dependency!

Is this a joke or am I missing something I have digikam installed but not amarok and I don't have any mono installed. I went to synaptice and clicked on amorok and task-kde4-extras and checked the dependencies under properties and mono is not listed nor does synaptic want to add mono if you mark them for installation. Neither libgpod or lib4gpod are listed as dependencies for digikam, amorak, task-kde4-extras or kipi either according to synaptic properties > dependencies. It is not April one is it? When KDE starts depending on mono I will drop it in an instant but that time is not here now.

[Padma]

The current update seems to make mono a dependency of these apps.  I saw mono was added in my update, so I went in and removed it.  It took task-kde-extras with it, because of digikam and amarok.  I have tried to re-add amarok and digikam, but they insist on re-adding mono, as well.

[Artwi]

There are more suspicious dependencies after update. For example you can't uninstall google-gadgets without kdebase4-workspace uninstalling
 

[Texstar]

There are more suspicious dependencies after update. For example you can't uninstall google-gadgets without kdebase4-workspace uninstalling
 

kdebase4-workspace is simply a meta package that contains no files only dependencies to install all goodies for kdebase4-workspace packages. kdebase4-workspace-core is the package that contains the workspace files.

[moniac]

There are more suspicious dependencies after update. For example you can't uninstall google-gadgets without kdebase4-workspace uninstalling
 

kdebase4-workspace is simply a meta package that contains no files only dependencies to install all goodies for kdebase4-workspace packages. kdebase4-workspace-core is the package that contains the workspace files.

Texstar  I just went and did the update Padma is talking about. It would not let me update without mono. I unmarked mono and did the update and it left off a lot of packages. I went back and individually installed the packages until I got to libgpod and lib4gpod. They have changed to require mono for digikam. Digikam is the same and really does not require mono to work. I keep old copies of the repos. I had backed up the repo to just before this last update. I set it up as the only repo synaptic can see and it installed digikam the kipi plugins and the two  libs libgpod and lib4gpod before they required mono. Could you go into those libs and take out the digikam mono requirements or what ever needs to be done. Please don't let PCLinuxOS KDE have to use mono or give us mono haters (linux free choice lovers) an opt-out option.

[Texstar]

There are more suspicious dependencies after update. For example you can't uninstall google-gadgets without kdebase4-workspace uninstalling
 

kdebase4-workspace is simply a meta package that contains no files only dependencies to install all goodies for kdebase4-workspace packages. kdebase4-workspace-core is the package that contains the workspace files.

Texstar  I just went and did the update Padma is talking about. It would not let me update without mono. I unmarked mono and did the update and it left off a lot of packages. I went back and individually installed the packages until I got to libgpod and lib4gpod. They have changed to require mono for digikam. Digikam is the same and really does not require mono to work. I keep old copies of the repos. I had backed up the repo to just before this last update. I set it up as the only repo synaptic can see and it installed digikam the kipi plugins and the two  libs libgpod and lib4gpod before they required mono. Could you go into those libs and take out the digikam mono requirements or what ever needs to be done. Please don't let PCLinuxOS KDE have to use mono or give us mono haters (linux free choice lovers) an opt-out option.

I've split out the mono from libgpod packages.

[moniac]

There are more suspicious dependencies after update. For example you can't uninstall google-gadgets without kdebase4-workspace uninstalling
 

kdebase4-workspace is simply a meta package that contains no files only dependencies to install all goodies for kdebase4-workspace packages. kdebase4-workspace-core is the package that contains the workspace files.

Texstar  I just went and did the update Padma is talking about. It would not let me update without mono. I unmarked mono and did the update and it left off a lot of packages. I went back and individually installed the packages until I got to libgpod and lib4gpod. They have changed to require mono for digikam. Digikam is the same and really does not require mono to work. I keep old copies of the repos. I had backed up the repo to just before this last update. I set it up as the only repo synaptic can see and it installed digikam the kipi plugins and the two  libs libgpod and lib4gpod before they required mono. Could you go into those libs and take out the digikam mono requirements or what ever needs to be done. Please don't let PCLinuxOS KDE have to use mono or give us mono haters (linux free choice lovers) an opt-out option.

I've split out the mono from libgpod packages.

I love you

[Padma]

Thank you, Texstar!

[longtom]

Texstar - I cannot believe you have done this!      Just for 2 anti-mono freaks? 

Now - this is what makes PCLinuxOS the one and only.   

Another round for my Texan friend over here ... and make it snappy!

[GOTHBITES]

+1

even though this sounds all  Greek to me no offense sproggy

[moniac]

Texstar - I cannot believe you have done this!      Just for 2 anti-mono freaks? 

Now - this is what makes PCLinuxOS the one and only.   

Another round for my Texan friend over here ... and make it snappy!

I am not a freak and don't appreciate your comments! The simile face is just a back door for you. If you really cared about linux being free from microsoft's claims of patent infringement you would do what you can to keep it out of PCLinuxOS's default installation. If you really want mono it is in the repos so jump on it. microsoft made promises for part of the code but not all of it and you know how much you can trust the evil thugs at micosoft. Everyone who has read just a little about mono knows it is not useful without using the code not included in the promise and I also just read it is not compatible with the GPL either.

[nindnarne]

I am not a freak and don't appreciate your comments! The simile face is just a back door for you. If you really cared about linux being free from microsoft's claims of patent infringement you would do what you can to keep it out of PCLinuxOS's default installation. If you really want mono it is in the repos so jump on it. microsoft made promises for part of the code but not all of it and you know how much you can trust the evil thugs at micosoft. Everyone who has read just a little about mono knows it is not useful without using the code not included in the promise and I also just read it is not compatible with the GPL either.

Yep, couldn't agree more. I was actually surprised to see this happen in the first place. Mono has about zero to do with KDE....so why include it? If we go down that line; whats next? Patent agreement with Microsoft?? ;-)

[longtom]

If you want to flamebait me about mono you picked the wrong one.  And I write what I like here in the framework of the forum rules.  If you really feel offended by my remark you are the one with the problem. 

Luckily I know that the general tone of the forum and the way the rest of us commute with each other will luckily be not affected by some fanatics of the one or other viewpoint, be it the politically correct one or not.

And another round for us over here ....