[Pkg-nx-group] New darcs repository

[Stefan Lippers-Hollmann]

Hello

On Monday 18 September 2006 00:51, Per Olofsson wrote:
> Hi,
>
> I'm working on the NX packages now, and I've set up some darcs
> repositories at: http://pkg-nx.alioth.debian.org/darcs/

Like Roberto C. Sanchez and Alexander Wirt already mentioned, this is 
probably a rather unfortunate VCS decision. I guess you weren't aware of
	svn://svn.debian.org/svn/pkg-nx/nxcomp/trunk/
	svn://svn.debian.org/svn/pkg-nx/nxcompext/trunk/
	svn://svn.debian.org/svn/pkg-nx/nxproxy/trunk/
still in early work progress based on NX 1.4 for the reasons stated below, 
but I'm actually more interested in your visions regarding NX packaging 
for debian, than in re- using existing efforts.


What are your plans regarding nx-X11/ nxagent, nxdesktop and nxviewer, 
the potential "server" backend (FreeNX or 2X Software Ltd. nxserver?) and 
a suitable client (if you plan to ship any client, nxssh and eventually 
nxprint, nxspool and nxesd)? 

Are you aware that there currently is no dfsg free (non-ia32/ i386) 
client for NX 2.0, while there are qtnx and 2X Software Ltd. nxclient 
(both for about 3-4 weeks) so far depending on NX 1.5 and both licensed 
under the GPL?

How do you plan to implement the file layout (FHS compliant or NoMachine 
like)?

What is your proposed time frame for getting the source into a releasable 
state, etch+1, etch+2? Especially considering that doing the necessary 
code overhauls most likely aren't supported by NoMachine and would 
effectively force you to become upstream yourself and fork the code 
base - or have you already settled this question with upstream?

How do you plan to counter the other issues I've enumerated [1]?

> Only debian/ directories are in the repositories. For example, to
> check out the nxcomp package, unpack the source, cd into the directory
> and run:

How do you plan to manage pristine upstream tarballs? You'll have to prune
a significant amount of unused code and non dfsg free parts, besides that 
NoMachine doesn't keep obsolete tarballs available for downloading.

> darcs get http://pkg-nx.alioth.debian.org/darcs/nxcomp/debian
>
> If you're in the Alioth group, you can push changes with:
>
> darcs push
> alioth.debian.org:../../groups/pkg-nx/htdocs/darcs/nxcomp/debian
>
> (I recommend creating a symlink in your Alioth home directory to make
> the path shorter.)

So far I've been working on getting 2X Software Ltd.'s code base for 
NX 1.5 [2] into a buildable, but by far not suitable for debian, state - 
very early work in progress is located at [3]. I tried to lay out a 
foundation for a general overhaul of the code base in cooperation with 2X 
Software Ltd., aiming for a long term solution for the questions mentioned 
above.

Predicted time frame for this task:
- 2-3 "man days" for a completely buildable source 
  - real time based on my available time probably a bit more than 2 
    weeks, usable inofficial packages shipping nxclient/ qtnx and nxserver
    in ~3 weeks.
- discussing and pushing changes "upstream" (2X Software Ltd.) 1-2 days
- merging useful changes from NoMachine NX and porting rdepends 2-3 months
- pruning sources and porting to X.org 7 <undefined>, probably 6-8 "man 
  weeks", accordingly longer given free time constraints.
- getting releasable packages for debian/ proper ~etch+1 at the earliest.

[1] http://lists.alioth.debian.org/pipermail/pkg-nx-group/2006-September/000136.html 
    and the sources referenced from it.
[2] http://code.2x.com/linuxterminalserver
[3] http://debian.tu-bs.de/project/kanotix/experimental/pool/main/n/nx/

Regards
	Stefan Lippers-Hollmann
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-nx-group/attachments/20060918/1931b1fa/attachment-0001.pgp