Development/FAQs/General FAQ/zh-cn

    From KDE TechBase
    Revision as of 04:57, 13 August 2012 by Fengchao (talk | contribs) (Created page with "<syntaxhighlight lang="text">[miscellany] global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \ config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la....")
    Other languages:

    我想要开发新的应用程序。有什么建议?

    我们都同意需要编写大量的 KDE 应用程序。但同时也有很多现有的 KDE 应用程序需要你的帮助。

    如果你想了解一下目前需要帮忙的地方,请看本页面

    在开始新的应用程序前,检查 KDE-Apps.org 上现有的应用程序,并在 kde-devel 邮件列表中进行咨询,看看是否有人已经开始类似的项目。

    我是开发人员,我要如何帮助 KDE 呢?

    尽管Calligra和KDevelop受到高度赞赏,它们只有极少数开发者,所以你可以从这里开始。提供帮助并不仅仅体现在加入KDE 工作空间或KDE平台库的开发。KDE 是高度模块化的,所以你不必了解整个系统就能每次改善某个独立的方面。

    您也可以在 kde-devel 邮件列表问问是否有人需要协助。使用KDE最新版,看看有否需要晚上的地方。主题生成器?konsole 计划编辑器?改善游戏?这些项目总是有小功能缺失。去实现它吧!

    你是熟悉或关注于特定领域吗?查看是否有相关的应用程序,可以获得您的帮助。或者自己写一个。KDE 需要更多非 geek 导向的应用程序。

    我不是开发者,我要怎样帮忙

    有大量不需要开发技术的任务。撰写应用程序评论帮助 KDE 推广(请见 kde-promo 邮件列表),帮助文件团队(请见 i18n.kde.org/doc),协助翻译(请见 i18n.kde.org),帮助过滤新增的 bug(请见 bugs.kde.org)等。

    在哪里可以找到 Konqi 龙的图像?

    The Konqi for some people SDK is at ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2
    It was posted to artist.kde.org before that site ceased to be updated.

    Further images are on KDE merchandise.

    贡献 KDE 需要什么样的水平?我应该学习什么?阅读什么?

    您需要了解 C++。阅读 Qt 的教学和浏览 Qt 的文件来熟悉 Qt。然后阅读KDE的教学和浏览架构和文件。您还可以阅读KDE的书籍。但你不用熟悉整个 KDE 的架构成为 KDE 开发者。使用 KDE 的技术是很容易的,所以集中在你真正需要的,你可以以后再学习其他部分。KDE TechBasedoc.qt.nokia.com (或者在您的 $QTDIR/doc/html) 是宝贵的资源,要善用它们。然后浏览原始码,寻找范例目录,看看其他应用程序的写法。读写程序代码是最好的学习方法。

    如何从 KDE git 或 SVN 仓库获取 KDE 软件?

    参阅开始页面的"从源代码编译和运行KDE软件"。

    可以在线访问 KDE 源码吗?

    可以

    我的 .subversion/config 应该怎样配置?

    [miscellany]
    global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
    config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
    *_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
    *.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
    *_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
    Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
    *.o *.lo *.la #*# .*.rej *.rej *.pyc
    

    让 svn diff 忽略空白并打印函数名:

    [helpers]
    diff-cmd = /usr/local/bin/_svndiff
    

    with the following in /usr/local/bin/_svndiff:

    #!/bin/sh
    exec /usr/bin/diff -b -u -p "$@"
    

    Don't forget to make /usr/local/bin/_svndiff executable.

    I want to put my app in KDE

    There are three requirements:

    • your app must compile with the latest version of KDE (git master or SVN trunk).
    • your app must be stable.
    • your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.

    See also the next question.

    Is it better to develop inside or outside KDE?

    As core developer Waldo Bastian explains in a copyrighted mail:

    Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

    Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

    On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

    You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

    In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

    BUT... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.

    It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

    How do I get write access to KDE repositories?

    See full article at Contribute > Get a KDE Contributor Account.

    Go to [KDE Identity] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

    Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

    Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. ~/.ssh/id_dsa.pub)

    See also #How do I create a SSH key?

    If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

    Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)

    A detailed list of rules you should follow when committing to KDE repositories are listed in the KDE Commit Policy.

    My app is not stable but I would like to have it in KDE

    As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

    I don't want to lose my SVN history.

    This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

    What is kdebindings?

    It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the binding page of TechBase.

    Does the feature freeze apply to playground?

    No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

    Can I have a stable and an unstable KDE on the same computer?

    Yes, check the Building 2 Versions documentation.

    How do I know which version of Qt/KDE I am using?

    kde-config and all kde programs accept --version as argument.

    Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?

    You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

    How can I checkout a single directory from a SVN module?

    Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

    For instance, to get only reaktivate from playground/utils: svn co -N /playground/utils; svn up reaktivate Then compile as usual.

    The same answer applies to the question "How do I get a single language out of kde-i18n?".

    If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

    How can I get one of the KDE application as a standalone tarball?

    kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

    How do I close my own bug reports?

    If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

    You can do that from your Subversion commit. To do so, append to your commit message a line like this:

    BUG: XXXXX where XXXXX is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

    Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

    How do I create a SSH key?

    SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

    Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen. When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

    If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

    For the practical part, the following command can be used to generate a SSH private/public key pair with ssh-keygen -t dsa This will create a private key as ~/.ssh/id_dsa and a public key as ~/.ssh/id_dsa.pub.

    There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,

    Host svn.kde.org 
    IdentityFile ~/.ssh/id_dsa_kde

    In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

    How can I monitor changes made by others?

    The kde-commits mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is CommitFilter which allows you to get notification for only those areas that interest you.