From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RDEPENDing on packages from overlays?
Date: Sat, 23 Apr 2011 04:02:24 -0700 [thread overview]
Message-ID: <4DB2B1C0.2050708@gentoo.org> (raw)
In-Reply-To: <4DB26C3C.8090602@gentoo.org>
On 04/22/2011 11:05 PM, Eray Aslan wrote:
> https://bugs.gentoo.org/show_bug.cgi?id=364445
> https://bugs.gentoo.org/show_bug.cgi?id=364401
>
> Basically, there are requests to add packages to RDEPEND in virtual/mda
> and virtual/mta that are not in the official tree but in sunrise.
>
> On one side, *DEPENDing on a package outside the tree doesn't seem
> right. Additionally, keeping track of all the overlays and their
> package versions, USE flags and flag changes are potentially too much to
> track. We will be making changes to a virtual package without testing
> whether it works.
I would assume that it's the overlay maintainers' responsibility to test
and report any problems. Any such problems would should affect the
overlay users, so it shouldn't cause any regression for users who don't
choose to use the overlay.
> 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.
> Comments on how to proceed?
Either way is fine. It's just a matter of whether or not collaboration
with the overlay is worthy of your time.
> Is it OK for a virtual to list a package
> which is in an overlay in RDEPEND?
Yes, that's fine. For || dependencies, repoman will be satisfied as long
as there at least one provider available for a given profile.
--
Thanks,
Zac
next prev parent reply other threads:[~2011-04-23 11:03 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 ` Zac Medico [this message]
2011-04-23 12:01 ` [gentoo-dev] " Nathan Phillip Brink
2011-04-23 12:07 ` Thomas Sachau
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=4DB2B1C0.2050708@gentoo.org \
--to=zmedico@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