RFS: vim-latexsuite

Franz Pletz fpletz at franz-pletz.org
Tue Apr 18 16:37:06 UTC 2006


On Tue, Apr 18, 2006 at 10:15:27AM -0400, Stefano Zacchiroli wrote:
> Sure, I will be happy to sponsor the upload.

Thanks!

> As you probably noticed I committed a few changes, mainly two:
> - cosmetic changes on debian/changelog which now is more coherent with
>   the format we use for vim's
> - added an alternative on vim-full where only vim-python was expected

Ah, right, vim-full also includes the scripting support for python.
Thanks.

> I have a remark about the version number, why is it 0.<date>. The common
> scheme for this is just <date>, can you please move it to that scheme?

Upstream has this version numbering scheme. I don't know why, perhaps they
will release a 1.0 someday? When converting to the <date> scheme wouldn't
there be problems when they actually release a 1.0?

> In addition to that: which layout are you using for svn-buildpackage
> (i.e. where do you put the upstream tarball)? I tried some but failed to
> found one that svn-buildpackage consider "default". (And yes, that means
> that so far I've been unable to build your package, but I'm lazy :))

Hmm, I just skimmed through the svn-buildpackage manpage and the howto
but there seems no option for svn-buildpackage to supply upstream
tarballs. Then I found the mergeWithUpstream property for debian/ which
instructs svn-buildpackage to take the upstream tarball from origDir
(in .svn/deblayout) and extract it to the build-area.

Looking at how you manage this in vim and vim7 it seems you fetch the
upstream tarballs into upstream/tarballs and extract them afterwards
(after cleaning up) in debian/rules.

Should I put the tarball into svn (vim-latexsuite/tarballs) and modify
debian/rules as you did with vim? Currently, I've got a working version
with mergeWithUpstream and changing debian/rules only a litte bit to
remove the tarballs/ directory so that dpkg-source doesn't find funky
changes.

Or is this all superfluous and should I just extract the tarball to
vim-latexsuite/ and use svn-upgrade for new upstream versions? As
vim-latexsuite is relatively small compared to vim this would also make
sense to me.

Sorry for all these perhaps silly questions, but I've never worked with
svn-buildpackage before.

Thanks,
Franz

-- 
Franz Pletz                   \  The Internet treats censorship as
www: http://franz-pletz.org/   \  damage and routes around it.
email: fpletz at franz-pletz.org   \  -- John Gilmore



More information about the pkg-vim-maintainers mailing list