[Pkg-tigervnc-devel] TigerVNC debian upload

[Yaroslav Halchenko]

NB Took Joachim's CC since I guess you are subscribed to the list ;-)

On Fri, 08 Mar 2013, Joachim Falk wrote:
> > I have pushed some cosmetic changes into git's master... only then 
> > realized  that I am not sure if that was correct course of action
> > or generic changes should go into squeeze-backport one first.

> > Joachim, please advise ;-)  meanwhile trying to build (for sid)
> No, I think checking in for master should come first. Wheezy is our
> first priority. I will back port the changes to squeeze.

yes! and I expected sid  to be close enough to wheezy at this point... I did
build for sid but haven't tested it -- I will try to build for wheezy
explicitly now and see how that one works.  If there is a divergence -- we
indeed would need to address it.

> >>> Well -- 2 of them are very logical, the 3rd one (actual 
> >>> tigervnc_1.2.0+X1.12.1.902.orig.tar.gz) seems to be just a
> >>> convenience empty one (with debian/README.Source included) to
> >>> get -tigervnc one into its own directory under... how necessary
> >>> such a step -- not sure.  Seems to unify things but on the
> >>> other hand puts additional (but tiny) unnecessary burden on the
> >>> archive.  Unless ftpmasters start complaining I would not mind
> >>> it.

> I think it is possible to do without the
> tigervnc_1.2.0+X1.12.1.902.orig.tar.gz. But I don't exactly know how
> to enable the corresponding mode in the
> source/{options,format,local-options}

what I meant is that tigervnc_1.2.0+X1.12.1.902.orig.tar.gz could
actually contain the tigervnc, i.e. replace  having
tigervnc_1.2.0+X1.12.1.902.orig-tigervnc.tar.gz

> >> besides that the README comes from debian/ and any changes to it
> >> would demand a new "upstream release"... kinda suboptimal
> Could you explain what exactly you mean with that? The README in
> tigervnc_1.2.0+X1.12.1.902.orig.tar.gz is removed anway.

ah -- may be  I got some older copy from 
http://xiao.jfalk.de/\~joachim/tigervnc ?

$> tar -tzvf <(wget -q -O- http://xiao.jfalk.de/~joachim/tigervnc/tigervnc_1.2.0+X1.12.1.902.orig.tar.gz)                  
-rw-rw---- joachim/joachim 2983 2012-06-14 07:02 tigervnc-1.2.0+X1.12.1.902/README.TXT


> We could also
> use an empty tigervnc_1.2.0+X1.12.1.902.orig.tar.gz. As I said above,
> it should be possible to remove tigervnc_1.2.0+X1.12.1.902.orig.tar.gz
> altogether, but I have not found the right combination of flags to
> enable this.

I am just trying to avoid having unnecessary (empty) file.  If there is no easy
way to ship tigervnc within the main .orig.tar.gz -- then sure, empty should
work as well, there is even an option to dpkg-source --create-empty-orig (which
could be included under debian/source/options)


> >>> May be there is more to it, Joachim could clarify.

> >> may be tigervnc submodule could get his subdir reincarnated and
> >> just serve the .orig.tar.gz ?  could you please rehearse the
> >> reason for that change?
> Well, at the moment we use a svn checkout of tigervnc. However, if
> tigervnc ever releases their own official tarball I planned to used them
> as the pristine tar.

yeap -- that would be better.  But if packaging would rely on having tigervnc/
subdirectory with its code (instead of just extracting it in the top
directory), then I guess having a -tigervnc.tar.gz (+ empty .orig.tar.gz) would
be the only option here (without repacking tigervnc's tarball into
.orig.tar.gz prepending tigervnc/ directory), right?

-- 
Yaroslav O. Halchenko
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Senior Research Associate,     Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834                       Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik