public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Sachau <tommy@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RDEPENDing on packages from overlays?
Date: Sat, 23 Apr 2011 14:07:21 +0200	[thread overview]
Message-ID: <4DB2C0F9.3090501@gentoo.org> (raw)
In-Reply-To: <4DB2B1C0.2050708@gentoo.org>

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

Am 23.04.2011 13:02, schrieb Zac Medico:
> On 04/22/2011 11:05 PM, Eray Aslan wrote:
>> On the other hand, we are making life (unneccesarily?) difficult for
>> overlay users by not incorporating the requested changes to the official
>> tree.
> 
> I don't imagine it's that much work to maintain a fork of the virtual.
> It's just an inconvenience for users since the version from the overlay
> might become temporarily outdated and cause problems with dependency
> resolution.

It may be no issue as long as the virtual does not change that much or as long as not more than 1
overlay forks the virtual. But as already written in Bugzilla, you create an issue for users, if you
have 2 overlays added, which both provide the package. Simple example, which i presented in Bugzilla:

If e.g. kde and sunrise overlay both provide an mta, they would both need a fork of virtual/mta. Now
one of those forks will be preferred and used, e.g. the kde one. This means, that you cannot install
the mta from sunrise to satisfy the virtual without additional manual work. The only way to solve
this properly without asking the user to manually adjust things is to just add all mtas from
overlays (maybe restricted to dev-controlled or -managed overlays) to virtual/mta in the main tree.


-- 
Thomas Sachau

Gentoo Linux Developer


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

  parent reply	other threads:[~2011-04-23 12:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-23  6:05 [gentoo-dev] RDEPENDing on packages from overlays? Eray Aslan
2011-04-23 10:28 ` [gentoo-dev] reconciling new-style virtuals with overlays, was: " Chí-Thanh Christopher Nguyễn
2011-04-23 11:15   ` Zac Medico
2011-04-23 13:25     ` Chí-Thanh Christopher Nguyễn
2011-04-23 11:32   ` Ciaran McCreesh
2011-04-23 13:28     ` Chí-Thanh Christopher Nguyễn
2011-04-23 13:37       ` Ciaran McCreesh
2011-04-23 14:47         ` Chí-Thanh Christopher Nguyễn
2011-04-23 14:57           ` Ciaran McCreesh
2011-04-23 15:50             ` [gentoo-dev] reconciling new-style virtuals with overlays Ulrich Mueller
2011-04-23 16:02             ` [gentoo-dev] reconciling new-style virtuals with overlays, was: RDEPENDing on packages from overlays? Chí-Thanh Christopher Nguyễn
2011-04-23 11:02 ` [gentoo-dev] " Zac Medico
2011-04-23 12:01   ` Nathan Phillip Brink
2011-04-23 12:07   ` Thomas Sachau [this message]
2011-04-23 12:08     ` Ciaran McCreesh
2011-04-23 13:05     ` Ulrich Mueller
2011-04-23 15:24       ` Zac Medico
2011-04-24  4:57         ` Eray Aslan
2011-04-24  5:39           ` Ulrich Mueller
2011-04-24  6:42             ` Eray Aslan
2011-04-24 20:35               ` William Hubbs
2011-04-23 11:03 ` William Hubbs
2011-04-23 13:07   ` Chí-Thanh Christopher Nguyễn
2011-04-23 11:08 ` [gentoo-dev] " Diego Elio Pettenò
2011-04-23 11:34 ` [gentoo-dev] " Ciaran McCreesh
2011-04-23 11:59 ` Thomas Sachau

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=4DB2C0F9.3090501@gentoo.org \
    --to=tommy@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