public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Drake Wyrm <wyrm@haell.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] SRC_URI component naming collision
Date: Sat, 25 Feb 2006 13:29:19 -0800	[thread overview]
Message-ID: <20060225212918.GA7304@phaenix.haell.com> (raw)
In-Reply-To: <200602251624.28125.pauldv@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]

Paul de Vrieze <pauldv@gentoo.org> 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

[-- Attachment #2: Type: application/pgp-signature, Size: 199 bytes --]

  reply	other threads:[~2006-02-25 21:31 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24 14:19 [gentoo-dev] SRC_URI component naming collision Ciaran McCreesh
2006-02-24 22:51 ` Jochen Maes
2006-02-24 23:09 ` Doug Goldstein
2006-02-25 15:24 ` Paul de Vrieze
2006-02-25 21:29   ` Drake Wyrm [this message]
2006-02-26 14:53     ` Paul de Vrieze
2006-02-26 19:45 ` Stuart Herbert
2006-02-26 19:56   ` Mike Frysinger
2006-02-26 20:30     ` Stuart Herbert
2006-02-26 20:00   ` Ciaran McCreesh
2006-02-26 20:46     ` Stuart Herbert
2006-02-26 21:04       ` Ciaran McCreesh
2006-02-26 21:30         ` Stuart Herbert
2006-02-26 21:40           ` Ciaran McCreesh
2006-02-26 22:13             ` Stuart Herbert
2006-02-26 22:31               ` Ciaran McCreesh
2006-02-27 10:02             ` Paul de Vrieze
2006-02-27 16:33               ` Ciaran McCreesh
2006-02-27 16:46                 ` Lance Albertson
2006-02-27 17:11                   ` Ciaran McCreesh
2006-02-26 20:02   ` Daniel Ostrow
2006-02-26 21:29 ` Robin H. Johnson
2006-02-26 21:54   ` Stuart Herbert
2006-02-26 22:02     ` Daniel Ostrow
2006-02-26 22:17       ` Stuart Herbert
2006-02-26 22:27         ` Ciaran McCreesh
2006-02-27  2:53         ` Daniel Ostrow
2006-02-27  3:25           ` Alec Warner
2006-02-27 10:05   ` Paul de Vrieze
2006-02-27 16:34     ` Ciaran McCreesh
2006-02-27 20:23       ` Robin H. Johnson
2006-02-28 14:16     ` Marius Mauch
2006-02-28 15:28       ` Paul de Vrieze

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060225212918.GA7304@phaenix.haell.com \
    --to=wyrm@haell.com \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox