On Friday 24 February 2006 15:19, Ciaran McCreesh wrote: > Two ways this one can occur. > > Way the first: foo-1.0 has a file in SRC_URI called foo.pdf. Then > foo-1.1 comes along, and has a different foo.pdf. > > Way the second: foo-1.0 has a file called examples-1.0.tar.bz2. bar-1.0 > also has a file called examples-1.0.tar.bz2. > > To avoid this, ensure that your packages use versioned SRC_URI > component names, and that the name part is something that's reasonably > likely to be unique (e.g. includes the package name). > > Side note: if the packages in question are fetch restricted, you're > screwed, and will not be able to add them to the tree. > > Current offenders shall be receiving bugs shortly, since That Which > Shall Not Be Named now checks for this.
What about introducing a new variable in the ebuild file:
DIST_PREFIX that has as default value ${PN}. This should not break anything
for unaware portage versions. For aware portage versions, the files would be
retrieved from ${DISTDIR}/${DIST_PREFIX} instead of ${DISTDIR}
Paul
--
Paul de Vrieze
Gentoo Developer
Mail: [EMAIL PROTECTED]
Homepage: http://www.devrieze.net
pgpgkYjJy21wO.pgp
Description: PGP signature
