On 08/12/2012 02:19 PM, Darrell Anderson wrote: > Many sound files are named with a KDE_* prefix. Everything works as is and > there is no requirement to rename the files. Yet in the spirit of renaming > for branding purposes, should we rename those files to TDE_*? > I say why?. The sound files are the KDE_xxx sound files. If we collect new ones for inclusion in TDE, then we make the new ones TDE_xxx sound files. I just don't see the need to rename the sound files unless we are preparing for a /usr/share/sound install (bad idea). I don't like injecting change where none is required. I see it as: (1) kde4 conflict or 'user-visible' or 'breaks backward compatibility' -> change to tde; (2) otherwise -> no need to change unneeded change always seems to bite us later. > There are two packages that contain the files: tdebase and tdeartwork. > Renaming and updating the respective make files is straightforward, as is > updating 11 default eventsrc config files in other packages in the source > tree. > > A remaining challenge is updating existing user profile eventsrc config files > to use the renamed files because existing eventsrc config files will be > referencing sound files with the KDE_* prefix, which no longer would exist. > > Currently we have no mechanism to update profile eventsrc files. We can write > a new shell script to perform the updates. The new script would be called by > the migratekde3 and called once from within starttde, like the r14-xdg-update > script. Or embed the updates in the migratekde3 and r14-xdg-update scripts. > > The renaming would be R14 only and not expected to be backwards compatible > with 3.5.13 sru. > Perfect... -- David C. Rankin, J.D.,P.E.