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] blocking mixed versions of split QT libraries
Date: Mon, 18 May 2009 18:11:04 +0100	[thread overview]
Message-ID: <20090518181104.11c7089e@snowcone> (raw)
In-Reply-To: <225000070905181001r4f9a9535rdbf0d07c4e6eabf0@mail.gmail.com>

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

On Mon, 18 May 2009 20:01:22 +0300
Alex Alexander <alex.alexander@gmail.com> wrote:
> is paludis expected to behave like portage in the near future
> regarding these blocks?

Probably not. My issue with the way Portage does soft blocks is that
it's way too arbitrary, fuzzy and ill defined.

There were plans to do blocks properly (include annotations that would
let the developer tell the package manager to point the user to a URL
explaining the block and how to resolve it) back before Zac went and
did his own thing. One of the goals was to tell the package manager
exactly what was meant by the block, allowing the package manager to
come up with a much more sensible and far less dangerous solution. If
those plans are ever revived, Paludis would support them.

> are there any plans to add support for these kinds of cases in the
> PMS? other sets of packages could probably benefit from such a feature
> as well.

I don't recall any existing discussion about such a feature (beyond me
moaning in pre-EAPI days about vim/gvim/vim-core breaking in the same
way Qt does). So... The way to start is probably by identifying the
problem in detail, and identifying other groups of packages affected by
similar issues, so we can work out what exactly it is we'd be looking
to fix.

-- 
Ciaran McCreesh

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

      reply	other threads:[~2009-05-18 17:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 10:04 [gentoo-dev] blocking mixed versions of split QT libraries Alex Alexander
2009-05-18 10:22 ` Alistair Bush
2009-05-18 16:34   ` Alex Alexander
2009-05-18 14:21 ` Ciaran McCreesh
2009-05-18 14:47   ` Petteri Räty
2009-05-18 14:52     ` Ciaran McCreesh
2009-05-18 17:15       ` Maciej Mrozowski
2009-05-18 17:26         ` Ciaran McCreesh
2009-05-18 18:05           ` Maciej Mrozowski
2009-05-18 18:19             ` Ciaran McCreesh
2009-05-18 19:08               ` Patrick Lauer
2009-05-18 19:20                 ` Ciaran McCreesh
2009-05-18 20:47                   ` Patrick Lauer
2009-05-18 20:55                     ` Ciaran McCreesh
2009-05-18 16:42   ` Alex Alexander
2009-05-18 16:51     ` Ciaran McCreesh
2009-05-18 17:01       ` Alex Alexander
2009-05-18 17:11         ` Ciaran McCreesh [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=20090518181104.11c7089e@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