From freenx-knx  Fri Nov 02 12:01:09 2007
From: Johnny Hughes <mailing-lists () hughesjr ! com>
Date: Fri, 02 Nov 2007 12:01:09 +0000
To: freenx-knx
Subject: Re: [FreeNX-kNX] freenx is dead !
Message-Id: <472B1185.70307 () hughesjr ! com>
X-MARC-Message: https://marc.info/?l=freenx-knx&m=119400769306912
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============0992834223=="

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0992834223==
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigB6C827969095AF17305BDB69"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigB6C827969095AF17305BDB69
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Durk Strooisma wrote:
>> I've been made aware of some even more important (and good) reasons fo=
r
>> not following the FHS when installing NX. More important reasons than
>> the ones I gave above. Read about them here:
>>
>>   http://www.nomachine.com/ar/view.php?ar_id=3DAR01C00130
>>
>> I can understand these. They are even "heavy" enough to keep violating=

>> the FHS even *after* the GPL source base of NX have moved to a newer
>> Xorg's FHS template layout (contrary to what I stated as "very likely
>> will be too much work").
>=20
> Honestly I'm not really impressed. Seems more like a configuration
> management issue and more important to developers than end users.
> Distributions like Debian need to change the structure anyway, as viola=
ting
> the FHS is not allowed. It's more work for them.
>=20
> The reasons NoMachine is giving could be true for almost every piece of=

> software. Nothing special in there. Still a lot of software projects ob=
ey
> the FHS. It's just a matter of preference. Apparently, NoMachine finds
> keeping everything in one place more important than being
> standards-complaint.
> Durk

Not sure what the question or problem is ... it is their code to manage
however they like.  It might be harder for debian (or CentOS in my case)
to make it FHS compliant, however there are plenty of projects where the
code isn't where we want it.  We just move it ... not sure why it is a
problem.


--------------enigB6C827969095AF17305BDB69
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHKxGFTKkMgmrBY7MRAlAuAKC3RSRfxqFq2wsQpWscE5HfAbufPACeKzlE
DACpBhuSQYdoCLyE5FA+D0Y=
=YLO3
-----END PGP SIGNATURE-----

--------------enigB6C827969095AF17305BDB69--

--===============0992834223==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:
  http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com/kb/ 

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