public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] SRC_URI component naming collision
Date: Tue, 28 Feb 2006 16:28:06 +0100	[thread overview]
Message-ID: <200602281628.07254.pauldv@gentoo.org> (raw)
In-Reply-To: <44045B53.3040804@gentoo.org>

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

On Tuesday 28 February 2006 15:16, Marius Mauch wrote:
> Check your mail archives for the old discussions about distfile name
> mangling (short version: a lot of stuff relies on distfile-name ==
> basename(src_uri), also if at all this would only be a long term
> solution due to compat issues involved).

For this reason a package might just specify a DIST_PREFIX. This would 
indicate a subdirectory in DISTDIR where the package is stored. When the 
package is merged, the files are copied from this directory instead of 
the DISTDIR directory. As the copy is already made, this behaviour should 
not be problematic. This does however solve 99% of the file name 
problems. The DIST_PREFIX value could be anything, with empty being the 
feature disabled, allowing for the much-wanted sharing of files between 
packages.

Even better is that this will even work with portage versions that do not 
support this feature. They will just store everything in DIST_PREFIX as 
it is now.

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net

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

      reply	other threads:[~2006-02-28 15:38 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
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 [this message]

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=200602281628.07254.pauldv@gentoo.org \
    --to=pauldv@gentoo.org \
    --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