27 Feb
2012
27 Feb
'12
10:16 p.m.
On Mon, 27 Feb 2012 10:59:08 -0500
Calvin Morrison <mutantturkey(a)gmail.com> wrote:
On 27 February 2012 10:44, David C. Rankin
<drankinatty(a)suddenlinkmail.com>wrote;wrote:
I know I'm probably trolling, but I'm
not sure making Trinity more
difficult to use than KDE SC 4 for former KDE 3 users is a good idea
either.
On 02/27/2012 09:11 AM, Aleksey Midenkov wrote:
Here is a solution.
Don't offer symlinks. Force users to memorize very minor changes in a
few differnet programs. If their scripts don't work - it will be
pretty obvious why. In our release announcement we will not what has
changed.
One thing that bugs me about Trinity is the fear of any change
whatsoever. Yes we want to continue the KDE3 tradition, no we are not
exactly kde3. If we make changes, users will have to adjust.
It is better to force them to learn the new names then down the road
having more nasty issues with symlinks and packaging and a whole mess
of crap that isn't a good idea. I suppose, it's not that so. From development
p.o.v. you are
forcing yourself to constantly sync different projects. From user
p.o.v. he is forced to install all packages 'tde-tdesymlinks'
depends on. Better is to develop common measure for packaging and
inform user once (remembering his choice).
I agree. You would need to base the package of symlinks on the
user's install
preference. Couldn't you use $TDEDIR to obtain the install location
and then set
the symlinks based on that?
--
David C. Rankin, J.D.,P.E.
Calvin