27 Feb
2012
27 Feb
'12
10:19 p.m.
On Mon, 27 Feb 2012 14:17:28 +0400
Aleksey Midenkov <midenok(a)gmail.com> wrote:
On Mon, Feb 27, 2012 at 12:45 PM, /dev/ammo42
<mickeytintincolle(a)yahoo.fr> wrote:
Why make the package depend on every Trinity package ? I don't think
dangling symlinks are such of a problem. Or perhaps it's just my
Slackware-originated "automatic dependencies are too complicated" way
of thinking.
On Mon, 27 Feb 2012 10:57:17 +0400
Aleksey Midenkov <midenok(a)gmail.com> wrote:
Making separate package is not necessary and not practical (it must
depend on all packages). Better to develop common postinst procedure
and include in every such package with info about renamed executables. I would strongly recommend after renaming such
scripts as startkde
to create symlinks to old names or at least ask user in postinst
to make such links!
I think a tdesymlinks packages would be a good idea. It would
include not only startkde->starttde, but also symlinks to every
renamed application such as twin, etc.
It would both:
-enable former KDE3 users to use the old names, just by installing
one package
-if the renaming is completed, enable new Trinity users to install
it in /usr alongside KDE SC 4/5.