Roman Savochenko via tde-users wrote:
> That is not about "manpower", the first, but about limiting udisks
> features and without proper informing in dialogues about used mounting
> parameters and mechanisms. And to add that, I need up to one hour, but
> prove that is a problem, it seems there will be one day and more.
>
If you have entry in fstab, you limit udisks - also TDE chooses fstab entry
first. This is correct.
May be TDE could be updated so that when you have udisks in the mount
options, that it would prefer using udisks over fstab.
I guess "formalizing" this as feature request will be more productive than growing this thread :)
Sorry, I installed NetBSD on new hard drive and I do not have access to my Linux hdd currently (there were only two sata power cables .. one goes into bluray writer/reader, other into hdd)
> The second, that is about positioning TDE as "with a primary goal of
> retaining the function and form of traditional desktop computers.", which
> means of the software working on "traditional" HW where this software
> appeared, but of course the "two standards way" brought KDE3 to breaking
> such possibility by cmake, tqtinterface and including new code with
> anchoring it to new interfaces without saving the old compatibility, so
> for Debian 7 the last is 14.0.10, for Debian 8 is 14.0.13, for Debian 9 is
> 14.1.0. That is, for new versions we must start to throw out the old HW
> also as for MancurtoScoft (MS)! The authoritarian development
> conception-process causes to I am patching this only for myself (and my
> users), also as CD-RW icons, playing DVD in Kaffeine and so on, after
> breaking those by the "local authority".
I am not aware of any TDE dependency on specific hardware. The compatibility
to the Debian system is driven by Debian. TDE supports the Debian version
as long as Debian supports this version.
And Debian versions come and go with its own set of restrictions .....
As for the rest Kaffeine for
example caused problems from the start to present. I am not aware that
some "local authority" did something on purpose to break something, but
honestly this is the reason I never liked or used it and I stick to
kplayer.
As far as I understood tqtinterface was merged into the main code ... what
old compatibility do you mean? You have to adjust the headers a bit and
recompile, which the devs are doing anyway for us.
Well, I think this is about infamous user/developer divide that failed to fail even with libre software. Software may be libre, but understanding it and rebuilding it locally often not really simple. Pushing changes upstream also not always work. You end up either doing A LOT of work, or swim with your distro's choices. I prefer Slackware exactly because it doesn't try to limit me from shooting myself into head with packaging/installing on my local machine. But even Slackware has limits of flexibility .....