summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20120220/58aed209/attachment-0001.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20120220/58aed209/attachment-0001.html')
-rw-r--r--zarb-ml/mageia-dev/attachments/20120220/58aed209/attachment-0001.html14
1 files changed, 14 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20120220/58aed209/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20120220/58aed209/attachment-0001.html
new file mode 100644
index 000000000..135a1a3fe
--- /dev/null
+++ b/zarb-ml/mageia-dev/attachments/20120220/58aed209/attachment-0001.html
@@ -0,0 +1,14 @@
+<p><br>
+在 2012-2-20 上午6:42,&quot;Kamil Rytarowski&quot; &lt;<a href="mailto:n54@gmx.com">n54@gmx.com</a>&gt;写道:<br>
+&gt;<br>
+&gt; Hello!<br>
+&gt;<br>
+&gt; 1.<br>
+&gt; What is the right implementation of an installation of *.desktop files? I saw every possible way of adding (build)require on desktop-file-utils. Is it necessary? What is the best way to implement it (of course in case of a mandatory requirement).<br>
+
+Most software will install .desktop files themselves.  In case we need to modify the menu categories, we often use desktop-file-install.</p>
+<p>&gt; 2.<br>
+&gt; Is allowed to use macros from jpackage-utils (the file name is/etc/rpm/macros.jpackage ) in a simple, normal non-java application? If yes, then is mandatory to add a buildrequirement of this package?<br>
+I think yes and yes. There are some packages BR kde4-macros, but they have no relation with KDE4.<br>
+&gt; Regards<br>
+</p>