'release' is fine with me.
Fine with me as well, but note that win/Release is created by the MS dev
tools. But as long as the "release" dir is only on the top level,
collisions should be avoided.
Rgds,
---
Peter Åstrand ThinLinc Chief Developer
Cendio AB http://w
'release' is fine with me.
Antoine Martin wrote:
> DRC wrote:
> > Not really sure if this qualifies as a contribution, since we'll be
> > using these scripts to build our own distribution packages. I'd rather
> > name it something like "build" or "dist" or "pkg". Perhaps we should
> > even consi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
DRC wrote:
> Not really sure if this qualifies as a contribution, since we'll be
> using these scripts to build our own distribution packages. I'd rather
> name it something like "build" or "dist" or "pkg". Perhaps we should
> even consider moving
Not really sure if this qualifies as a contribution, since we'll be
using these scripts to build our own distribution packages. I'd rather
name it something like "build" or "dist" or "pkg". Perhaps we should
even consider moving the existing packaging stuff, like tigervnc.iss,
into this new direc
On Thu, 08 Oct 2009 12:32:15 -0500
DRC wrote:
> I want to start putting together packages for all platforms, including
> Ubuntu, but I need to know where I can check in the relevant build scripts.
>
I have no strong opinions on the matter. contrib/ perhaps?
Rgds
--
Pierre OssmanOp
I want to start putting together packages for all platforms, including
Ubuntu, but I need to know where I can check in the relevant build scripts.
Antoine Martin wrote:
> On the subject of packaging.
>
> This post mentions the likely availability of packages for Ubuntu with
> the 1.0 release:
> ht
On the subject of packaging.
This post mentions the likely availability of packages for Ubuntu with
the 1.0 release:
http://www.mail-archive.com/tigervnc-us...@lists.sourceforge.net/msg2.html
The Ubuntu tracker is here:
https://bugs.launchpad.net/ubuntu/+bug/343842
Now that 1.0 is out, is any
One of the things I'm going to want to do as I start migrating from
TurboVNC to TigerVNC is to develop packaging scripts that will assist in
generating TigerVNC nightly builds and distribution packages that are
compatible with the same set of platforms as TurboVNC. I traditionally
have included th
