Paul de Vrieze <[EMAIL PROTECTED]> wrote: > On Friday 24 February 2006 15:19, Ciaran McCreesh wrote: [snip] > > 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).
Unfortunately, that's not always a possibility. I've bugged at least one
upstream about non-versioned sources. How does one work around that if
they won't fix it?
> 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}
That introduces a problem of redundancy. In some cases, more than one
package will use a given set of sources, and it will need to be fetched
and stored once for each package. Perhaps defaulting DIST_PREFIX to ""
and allowing it to be used for workarounds in the odd cases could work.
Just for the sake of demonstration, the following should show a list of
the source files which are used multiple times on any given system and
how many times they are used:
emerge -p --fetch-all-uri --emptytree world 2>&1 1>/dev/null |
sed -e '/^$/d;s/.*\///' |
sort | uniq -D | uniq -c | sort -n
--
There are problems in today's world that cannot be
solved by the level of thinking that created them.
-- Albert Einstein
pgpZArvY0rtCn.pgp
Description: PGP signature
