--- Stefan Lippers-Hollmann <[EMAIL PROTECTED]> wrote:
> Since these packages aren't in debian and won't become ready for debian in 
> the etch timeframe (if it will be possible to get them into a releasable 
> state for etch+1 remains to be seen [1]), the debian BTS is probably not 
> the best place for discussing unofficial packages. A more appropriate list 
> would probably be [2], [3] or the listed package maintainer directly (wich 
> would be me).

Noted though this info should really be listed on the debian wiki freenx
page (http://wiki.debian.org/freenx), no ?  The debian freenx wiki seems
to be lacking a great deal of info especially which you had just noted
with your recent reply.  If someone were to start on what I embarked upon
a week or so ago I'm not sure he/she would come to realize all this info
as it isn't pointed to from anywhere...

> > The package is available on a number of non-official repositories/sites;
> > I got mine with,
> >
> >  deb     http://packages.debianbase.de/testing/i386/nx/ ./
> 
> I'm in no way affiliated with that repository, but a short look at the 
> *.changes files suggest that those may be a very outdated rebuild of my 
> source packages, definately in no way X.org 7 compatible and 
> lacking quite a lot of changes done over the last year.

That and others are listed on the "official" freenx homepage,

  http://freenx.berlios.de/download.php

maybe that page should be updated as well (and a link added to point to
the debian freenx wiki page).

> > Note the changes listed on that wiki page are also required for
> > freenx to work properly.  I mailed a couple of people about
> > updating the wiki page with the info noted in this bug report
> > (you might want to follow-up with the wiki page's maintainer
> > as well).
> 
> The proposed changes are not sufficient for proper NX 2.0 compatibility and 
> will result in an installation that's neither stable for NX 1.5, nor NX 2.0 
> connections; a NX 1.5 client is the better option for now.

Well it works fine for me (with all the changes noted) using a 2.0 NXClient.
Keep in mind that whomever is interested in NX is most likely to download
the 2.0 client as that is the one listed and propagated by the nomachine.com
homepage (1.5 NX clients are very hard to find though that is not a central
issue).

> Probably more important might be the question why I haven't updated to NX 
> 2.0 yet...

As noted, do please share this info somewhere hopefully on the debian
freenx wiki page (note that a google search for 'freenx' doesn't even
list the debian NX list).  Do keep in mind also that most of those asking
questions on the web and requesting assistance are using Windows Clients
to connect to linux servers - as such they have very differing needs and
are forced to use newer 2.0 clients (more likely than not).  You are
addressing this from a linux to linux point-of-view which is perfectly
fine, it would be wise though to potentially address the other users'
needs as there are many (like me) who continue to look for a proper NX
server to be used with a 2.0 windows client.

Should I continue to use my hacks or revert to using what you have in
the repository as a starting point ?

Thanks for your complete email and prompt reply.

Regards,

 - Nadim


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to