| 1 |
On Saturday 25 February 2006 22:29, Drake Wyrm wrote: |
| 2 |
> > What about introducing a new variable in the ebuild file: DIST_PREFIX |
| 3 |
> > that has as default value ${PN}. This should not break anything for |
| 4 |
> > unaware portage versions. For aware portage versions, the files would |
| 5 |
> > be retrieved from ${DISTDIR}/${DIST_PREFIX} instead of ${DISTDIR} |
| 6 |
> |
| 7 |
> That introduces a problem of redundancy. In some cases, more than one |
| 8 |
> package will use a given set of sources, and it will need to be fetched |
| 9 |
> and stored once for each package. Perhaps defaulting DIST_PREFIX to "" |
| 10 |
> and allowing it to be used for workarounds in the odd cases could work. |
| 11 |
|
| 12 |
I don't think that there is redundancy often. For some packages there might |
| 13 |
be, but those could set the value. There are however many packages that come |
| 14 |
with files like patch.4.2.52.4 (for sys-libs/db-4.2.52). From the name it's |
| 15 |
impossible to know what it belongs to. And the fact that there is no |
| 16 |
collision is just by chance, not by name convention. |
| 17 |
|
| 18 |
Paul |
| 19 |
|
| 20 |
-- |
| 21 |
Paul de Vrieze |
| 22 |
Gentoo Developer |
| 23 |
Mail: pauldv@g.o |
| 24 |
Homepage: http://www.devrieze.net |
Archives