public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] What are blocks used for?
Date: Wed, 16 Apr 2008 09:48:36 +0100	[thread overview]
Message-ID: <20080416094836.5375f853@snowcone> (raw)
In-Reply-To: <18437.48017.68913.723605@a1i15.kph.uni-mainz.de>

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

On Wed, 16 Apr 2008 10:40:49 +0200
Ulrich Mueller <ulm@gentoo.org> wrote:
> I don't know if it would be feasible from a package manager point of
> view, but couldn't some (most?) blockers be avoided if there was some
> means to transfer ownership of installed files from one package to
> another?

From a package manager point of view, it's probably easier to know that
a transfer of ownership will take place (or, more specifically, that
collisions between two packages as part of an upgrade or replace
process are ok) than to deal with specific files. It's probably easier
to write ebuilds that way too -- providing explicit lists gets very
messy if we start talking about things that include libdir or bits of
CHOST or Ruby versions or whatever in their filenames.

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-04-16  8:48 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-16  5:24 [gentoo-dev] What are blocks used for? Ciaran McCreesh
2008-04-16  5:54 ` "Mateusz A. Mierzwin'ski"
2008-04-16  6:34   ` Ciaran McCreesh
2008-04-16  6:06     ` Luis Francisco Araujo
2008-04-16  7:26     ` Michael Haubenwallner
2008-04-16  7:34       ` Branko Badrljica
2008-04-16 14:56   ` Richard Freeman
2008-04-16 17:05     ` "Mateusz A. Mierzwin'ski"
2008-04-16 18:41       ` Petteri Räty
2008-04-16  7:24 ` Donnie Berkholz
2008-04-16  7:52   ` "Mateusz A. Mierzwin'ski"
2008-04-16  7:46     ` Ciaran McCreesh
2008-04-16 11:56     ` [gentoo-dev] " Duncan
2008-04-16  7:56   ` [gentoo-dev] " "Mateusz A. Mierzwiński"
2008-04-16  7:55     ` Bo Ørsted Andresen
2008-04-16  8:15       ` "Mateusz A. Mierzwiński"
2008-04-16  8:21         ` Bo Ørsted Andresen
2008-04-16 14:53           ` Richard Freeman
2008-04-16 17:01             ` "Mateusz A. Mierzwiński"
2008-04-16  8:04     ` Ciaran McCreesh
2008-04-16  8:18       ` "Mateusz A. Mierzwiński"
2008-04-16  8:13         ` Markus Rothe
2008-04-16  9:07           ` "Mateusz A. Mierzwiński"
2008-04-16  9:03             ` Ciaran McCreesh
2008-04-16  9:11               ` Wulf C. Krueger
2008-04-17 16:40             ` Dawid Węgliński
2008-04-16 12:04         ` [gentoo-dev] " Duncan
2008-04-16 12:29           ` "Mateusz A. Mierzwiński"
2008-04-16 12:30             ` Marijn Schouten (hkBst)
2008-04-16 16:59               ` "Mateusz A. Mierzwiński"
2008-04-16 21:24                 ` Andrej Kacian
2008-04-16  8:40       ` [gentoo-dev] " Ulrich Mueller
2008-04-16  8:48         ` Ciaran McCreesh [this message]
2008-04-17 20:02         ` Enrico Weigelt
2008-04-17 19:31   ` Enrico Weigelt
2008-04-16 10:16 ` Bernd Steinhauser
2008-04-17 19:51   ` Enrico Weigelt
2008-04-17 20:15     ` Vlastimil Babka
2008-04-18  1:11     ` [gentoo-dev] " Duncan
2008-04-17 17:58 ` [gentoo-dev] " Enrico Weigelt
2008-04-17 19:08   ` Vlastimil Babka
2008-04-17 20:07   ` Vlastimil Babka

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=20080416094836.5375f853@snowcone \
    --to=ciaran.mccreesh@googlemail.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