[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freenx-knx
Subject:    Re: [FreeNX-kNX] Compiling NX1.5.0 on amd64
From:       Xiong Jiang <linuster () gmail ! com>
Date:       2005-09-24 16:55:32
Message-ID: 9b5164430509240955261637f1 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


It's the package that released by NoMachine. Anywhere is it stated that the
files in nx-X11/lib/X11was not written by your people and supposed to be th=
e
same Xlib code of XFree86/X.org distributions?

Your knowledge base is so 'user friendly' that it is short of information
that developers would need. For example, reading through the 'building NX
components' article doesn't solve the compilation problems I met at all.

You know I am not trolling. I have spent several nights on it, and have
reported the compilation attempt at length. I understand that critical word=
s
are hard to digest but if you think this is still trolling I could say
nothing else. No more flamebait, just feel frustrated by the current NX
package. It could only be mitigated after somebody managed to get deb/rpm
package done/patched.

Xiong

On 9/24/05, Gian Filippo Pinzari <pinzari@nomachine.com> wrote:
>
> Xiong Jiang wrote:
> > I am still quite surprised about the package being released in such a
> > shape. Maybe NoMachine is short of resources as well.
>
> Yes, we are short of resources :-). Anyway, did you realize that the code
> you are talking about was not written by us but it is supposed to be the
> same Xlib code of the XFree86/X.org distributions?
>
> Instead of trolling, why don't you spend the time to compare the code wit=
h
> the latest XFree86/X.org versions? Maybe the fix (if it was actually a
> bug)
> has been merged in the XFree86/X.org code but not in nx-X11, for example
> because our builds have never come through the same bug.
>
> BTW, I strongly suggest you take a look at the NoMachine KB and at the
> other documents. They explain at length why you should keep the NX libs
> and the native X11 libs in separate directories.
>
> /Gian Filippo.
>
>
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX@kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
>

[Attachment #5 (text/html)]

It's the package that released by NoMachine. Anywhere is it stated that
the files in nx-X11/lib/X11was not written by your people and supposed
to be the same Xlib code of XFree86/X.org distributions?<br>
<br>
Your knowledge base is so 'user friendly' that it is short of
information that developers would need. For example, reading through
the 'building NX components' article doesn't solve the compilation
problems I met at all.<br>
<br>
You know I am not trolling. I have spent several nights on it, and have
reported the compilation attempt at length. I understand that critical
words are hard to digest but if you think this is still trolling I
could say nothing else. No more flamebait, just feel frustrated by the
current NX package. It could only be mitigated after somebody managed
to get deb/rpm package done/patched.<br>
<br>
Xiong<br><br><div><span class="gmail_quote">On 9/24/05, <b class="gmail_sendername">Gian Filippo \
Pinzari</b> &lt;<a href="mailto:pinzari@nomachine.com">pinzari@nomachine.com</a>&gt; \
wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: \
0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Xiong Jiang wrote:<br>&gt; I am still quite surprised about the \
package being released in such a<br>&gt; shape. Maybe NoMachine is short of resources as \
well.<br><br>Yes, we are short of resources :-). Anyway, did you realize that the code <br>you are \
talking about was not written by us but it is supposed to be the<br>same Xlib code of the XFree86/X.org \
distributions?<br><br>Instead of trolling, why don't you spend the time to compare the code with<br>the \
latest XFree86/X.org versions? Maybe the fix (if it was actually a bug) <br>has been merged in the \
XFree86/X.org code but not in nx-X11, for example<br>because our builds have never come through the same \
bug.<br><br>BTW, I strongly suggest you take a look at the NoMachine KB and at the<br>other documents. \
They explain at length why you should keep the NX libs <br>and the native X11 libs in separate \
directories.<br><br>/Gian \
Filippo.<br><br><br>_______________________________________________<br>FreeNX-kNX mailing list<br><a \
href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a> <br><a \
href="https://mail.kde.org/mailman/listinfo/freenx-knx">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br></blockquote></div><br>




_______________________________________________
FreeNX-kNX mailing list
FreeNX-kNX@kde.org
https://mail.kde.org/mailman/listinfo/freenx-knx


[prev in list] [next in list] [prev in thread] [next in thread]