Bug#654924: Fwd: Re: TigerVNC 1.0.90 src debs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 04.03.2012 19:44, schrieb Mike Gabriel:
> Hi Joachim,
>
> On So 04 Mär 2012 14:42:50 CET Joachim Falk wrote:
>
>>> I'd suggest to sync your Git to Alioth and continue/collaborate there.
>>> Do you have an account on Alioth? If not, I'd suggest registering and
>>> then apply for membership in the group ,,collab-maint''.
>> Ok, I have registered as jfalk-guest and applied for the project
>> pkg-tigervnc. Between, I fixed all the built errors for Xvnc.
>
> Downloading the xorg packaging tree for building the package does not
> look like the right approach for building Xvnc to me. I'd rather think
> that Xvnc can be built against the available Xorg headers on the build
> system.
I don't think so. I don't really download the xorg tree but the debian
package for building various X11 servers (X, xnest, xdmx, xvfb, etc.).
This package is already striped down to use the available system libs
and headers to built the servers. The only development stuff this
package provided is xserver-xorg-dev, which containts only headers.
These are used to develop driver, which are loaded by the X11 server.
So it should be sufficient to built the vnc.so component of tigervnc.
However, I don't think that it is sufficient to built the standalone
Xvnc X11 server.
> I am not sure if your Git repository works the way it currently is
> constructed. At least it looks like a not-so-usual packaging repos.
> I am not an overall expert but what I prefer is using tools like
> git-import-orig and pristine-tar.
Well the tigervnc and xorg stuff are integrated as subprojects into the
top project. I admit the tigervnc stuff is a svn checkout.
The real question is: How do we handle patches on top of the orig
sources. Either we use quilt for this then the subprojectness of xorg
and tigervnc is no problem. Otherwise we drop quilt and use native git
management for both tigervnc and xorg. However, in this case we have
to import a fully patched version of the xorg tree. Otherwise,
the xorg quilt patches would be applied over our modifications.
That is a pretty unsatisfactory situation.
>
> To give some insight in what I mean I uploaded a point where I would
> start from to my Git site:
> http://code.das-netzwerkteam.de/gitweb?p=debian/tigervnc.git;a=summary
>
> For a better overview, please check out some other packaging projects I
> am involved in:
> http://code.das-netzwerkteam.de/gitweb?p=debian/x2goclient.git;a=summary
>
>> Now the install stage has a problem. Furthermore, we will need
>> to modify the tigervnc configuration to use an external fltk if
>> possible. I think, we also need to check what else tigervnc uses from
>> internal sources.
>
> The internally shipped sources appear to be in upstream's common folder.
> These source should be replacable by Debian package header files shipped
> with Debian sid.
>
> Unfortunately, I do not have the time I would like to give to this
> project, I hope for better times during the next couple of weeks. :-(
>
> Greetings,
> Mike
>
>
Regards,
Joachim
- --
Joachim Falk <Joachim.Falk@gmx.de>
You can always tell a really good idea by the enemies it makes.
--programmers' axiom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJPU9kBAAoJEIjUIAk+3OYM12wP/jR4uVG87p+0X3lIoiZhZmO/
6ZCGjaP0Dr0kypulQNVyhhTkrHFYp7zlx9Pge9TXQzNHHm7MTiTuM/fSNAAc0YT2
cHVov37vttIc6sUcD1SRFIT1xeBkNmw4zoDPIaJDWrE311C3dn0GZDXpGbBMDBcD
la2M7vuZxFQgLokxI4prul2vjKLjRXfCfUrpp8zudZT4Zfc5lGg2t++sUeACn8pw
TvloNP3lgXc6SeSK84lD7qGDLt6GGzFysgmgh5TFs3nJ9F8t8sRMKJtIKkW8AYX0
H4KfQkWcYCWAeKzicaX2lq9B3JFEprxLBxNGX1F2pFustpA7Hx4Nh8GAv5OkE5f8
oMbWacXTmU3uWgq4R8jwhtEuE73NaiiCyA6YeTCRqNBWx5kYe7Rzgo6IUDM192Rc
K6FKpYGmfpl2I1PmDLMTtLR1A3UXVkIuk29tfYm2UDSEEBFW3wPv+LNUWjr2gpVz
5DFZCXD4m8UmkR7IzNyS3El/Suz2UZV4Geaj32eCLxJrKfN2FDozVUQjSz1IiVxG
BuTWSRAatS+yU+SRwm1Scoc6WNuu4WnIirCzrWcTvgFeU7nnCPnR5s/FSyFeJQ9U
6P/Q3BE6p4V1JSdMrwB+v8LKJjlUsmHMTOfr2egOWtoJSmV82AaNKSLLS40ZUgvj
g5Qu6UO+sy15MBGNmmuD
=9H3N
-----END PGP SIGNATURE-----
Reply to: