27 Feb
2012
27 Feb
'12
3:11 p.m.
On Mon, Feb 27, 2012 at 5:53 PM, David C. Rankin
<drankinatty(a)suddenlinkmail.com> wrote:
On 02/27/2012 02:45 AM, /dev/ammo42 wrote:
+1,
A symlink packages is a simple fix to a lot of potential problems. By putting
symlink control in a single package, you also gain control over the symlink
issues that users are bound to create them on their own, and can easily
update/revise the symlink setup by updates to a single package. I think it is a
good idea. Something like 'tde-tdesymlinks' or 'trinity-tdesymlinks'
sounds like
a reasonable name.
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 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.