[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dpkg-source v2

Anthony Towns wrote:
> > like this:
> >  98de5a37e7ff94ba30607671176e8a2c 13852125 evolution_1.0.7.orig.tar.gz
> >  5baeb94fb934d0bf783ea42117c400be 1954117 evolution:db_3.1.17.orig.tar.gz
> >  00fdddef14f104800edbba00e67dabf3 16806 evolution:debian_1.0.7-2.tar.bz2
> Erm. Having:
> 	evolution_1.0.7.orig.tar.gz
> 	evolution_db_1.0.7.orig.tar.gz
> 	evolution_1.0.7-2.diff.tar.gz
> 	evolution_1.0.7-2.dsc

I think you're lagging, as I later proposed the same.

> is probably do-able. Although you could end up with conflicts if your
> Debian revision (<rev>) ended with ".orig" -- foo.deb 1.3-4.orig, to
> foo.deb 1.3-4-5 would have the Debian patch for 1.3-4.orig be called
> "foo_1.3-4.orig.tar.gz" and the 1.3-4 upstream tarball would also be
> called that.  So it'd probably be better to expect the Debian stuff to
> end in .diff.{gz,bz2,tar.gz,tar.bz2,zip}, giving:

Detached .diff.gz's should not be needed at all with the nw source
format as they go into debian/patches/ and that is tarred up. Since the
debian/ directory tarball has 'debian' in its name and the other peices
don't, there is no ambiguity with version numbers as you describe.

> Hrm. Does it really make sense to put the <sub> name before the version?
- 	evolution_1.0.7-2.diff.tar.gz
+       evolution_1.0.7-2.debian.tar.bz2
> 	evolution_1.0.7-2.dsc
> 	evolution_1.0.7.orig.tar.gz
> 	evolution_1.0.7_db.orig.tar.gz
> ..would seem somewhat nicer, and easier to parse, and work with generally.

Yes it may make sense to do this.

see shy jo

To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: