| 1 |
On Friday 24 February 2006 15:19, Ciaran McCreesh wrote: |
| 2 |
> Two ways this one can occur. |
| 3 |
> |
| 4 |
> Way the first: foo-1.0 has a file in SRC_URI called foo.pdf. Then |
| 5 |
> foo-1.1 comes along, and has a different foo.pdf. |
| 6 |
> |
| 7 |
> Way the second: foo-1.0 has a file called examples-1.0.tar.bz2. bar-1.0 |
| 8 |
> also has a file called examples-1.0.tar.bz2. |
| 9 |
> |
| 10 |
> To avoid this, ensure that your packages use versioned SRC_URI |
| 11 |
> component names, and that the name part is something that's reasonably |
| 12 |
> likely to be unique (e.g. includes the package name). |
| 13 |
> |
| 14 |
> Side note: if the packages in question are fetch restricted, you're |
| 15 |
> screwed, and will not be able to add them to the tree. |
| 16 |
> |
| 17 |
> Current offenders shall be receiving bugs shortly, since That Which |
| 18 |
> Shall Not Be Named now checks for this. |
| 19 |
|
| 20 |
What about introducing a new variable in the ebuild file: |
| 21 |
DIST_PREFIX that has as default value ${PN}. This should not break anything |
| 22 |
for unaware portage versions. For aware portage versions, the files would be |
| 23 |
retrieved from ${DISTDIR}/${DIST_PREFIX} instead of ${DISTDIR} |
| 24 |
|
| 25 |
Paul |
| 26 |
|
| 27 |
-- |
| 28 |
Paul de Vrieze |
| 29 |
Gentoo Developer |
| 30 |
Mail: pauldv@g.o |
| 31 |
Homepage: http://www.devrieze.net |
Archives