[Pkg-octave-devel] Filing ITPs for the octave-forge pkgs
Thomas Weber
thomas.weber.mail at gmail.com
Thu Feb 28 13:21:43 UTC 2008
Am Donnerstag, den 28.02.2008, 10:17 +0100 schrieb Rafael Laboissiere:
> * Ólafur Jens Sigurðsson <ojsbug at gmail.com> [2008-02-28 03:33]:
>
> > > 2.) get-oct-pkg-src.pl has 45 lines of Perl code in order to download a
> > > package. The very first line of that code is already a mystery to me.
> > > Octave's watch file has 2 lines, one being the watch file's version.
>
> Yes, you are right, I duplicated many of the functionalities of uscan in
> that script. I will think a little bit further about this. However, notice
> that uscan would generate a wrong orig.tar.gz tarball for us. For the
> octave-forge packages, we need a tarball inside a tarball.
Okay, maybe I'm totally misunderstanding get-oct-pkg-src.pl, but does it
retar the tarball? A simple download is possible with the attached files
(it contains a dummy changelog, uscan wants a full infrastructure).
And according to uscan's manpage:
==========================================================================
The newest updates are retrieved [...] and if specified in the
watchfile, a program may then be executed on the newly downloaded
source.
==========================================================================
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: audio-0.9.9.tar.gz
Type: application/x-compressed-tar
Size: 403 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-octave-devel/attachments/20080228/a4fc3a8e/attachment.bin
More information about the Pkg-octave-devel
mailing list