Message: previous - next
Month: January 2012

Re: [trinity-devel] Trinity Renaming Project

From: L0ner sh4dou <sh4dou@...>
Date: Mon, 9 Jan 2012 13:52:06 +0100
2012/1/7 Timothy Pearson <kb9vqf@...>:
>>> Yesterday I downloaded a mirror image
>>> of the GIT repository. 3.9 GB. :)
>>> I have been updating and revising my build scripts with
>>> many obvious things but I suspect the renaming project will
>>> throw a few speed bumps into the build process.
>>> The etherpad has helped some. Yet is there anything
>>> specific or generic we need to know? A list of "gotchas"?
>>> Environment variables that have not been renamed? Etc.
>> Are all known environment variables renamed?
> Probably not.  As you or others run across them they should be added to
> the end of the renaming Etherpad so that I am aware of them.
>> To what extent will the renaming project continue? Although core level
>> packages names are changed, and a few various source files, such as
>> tdeversion.h, I notice only two run-time apps have been renamed: kdesu to
>> tdesu and kdesudo to tdesudo.
> I don't want to get into renaming applications.  tdesu and tdesudo were
> just so obvious that I had to rename them. ;-)
>> Have other apps been renamed?
> Not that I know of, except some core apps that users shouldn't run
> manually (such as kwin->twin
>> Will other apps or packages be renamed? For example, koffice to toffice
>> (kword to tword, etc.)?
> Probably not, unless we are asked by another project.
Well, some probably should be renamed over time as they will become
something else than original apps. Beside this will prevend confusion
among users. From the packages wievpoint our akregator isn't quite the
same app as kde4 akregator. For packaging some kind of prefix should
be added (like in ubuntu packages if I recall correctly).