On Mon, Jul 22, 2002 at 10:27:12PM -0400, Colin Walters wrote:
> walters@space-ghost> l evolution-1.0.7
> drwxr-sr-x 50 walters src 4096 2002-07-21 03:01 db-3.1.17
> drwxr-sr-x 30 walters src 4096 2002-07-21 03:01 evolution-1.0.7
Is this significantly better than having db3.1_3.1.17.dsc and
db3.1_3.17_i386.deb and/or db3.1-src_3.1.17_all.deb in the archive,
and setting evolution to Build-Depend: on it as necessary?
If you say that the multisource format is only for packages whose
upstream source is split into multiple files, rather than for cross-source
dependencies and such, you could expect that the version number on each
of the files will be the same.
That'd make it a fair chunk easier to work out what to download
too. Rather than having to check the .dsc for the exact version of
evolution_db you need, you can just grab:
pool/main/e/evolution/evolution{_*,}_1.0.7.{orig.tar.gz,dsc}
and
pool/main/e/evolution/evolution_1.0.7-2.diff.tar.gz # or whatever
If you do this, you can associate ./$dir with
../${src}_${dir}_${ver}.orig.*, which seems like it should be all you
need to do. If the $dir orig archive doesn't exist, $dir is part of the
main orig archive, or has been added in the debian patches.
> Actually, a third solution occurs to me; we create another file,
> source-control.xml, which is separate from debian/control, and would
> allow you to customize all these things. Yeah. Now that I think about
> it, this solution is probably the best.
XML? What's the incredibly good reason not to stick with the dpkg/rfc822
format that everything else uses that I must be missing?
Cheers,
aj
--
Anthony Towns <aj@humbug.org.au> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.
``If you don't do it now, you'll be one year older when you do.''
Attachment:
pgp7zk9B1AE8J.pgp
Description: PGP signature