From: "Jörg Schaible" <joerg.schaible@gmx.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Re: Re: Changes in installed ebuilds
Date: Fri, 27 Jun 2014 00:04:23 +0200 [thread overview]
Message-ID: <loi5d7$n1j$1@ger.gmane.org> (raw)
In-Reply-To: 20140626091328.425f7ec2@pomiot.lan
Michał Górny wrote:
> Dnia 2014-06-26, o godz. 00:48:02
> Jörg Schaible <joerg.schaible@gmx.de> napisał(a):
>
>> hasufell wrote:
>>
>> > Kristian Fiskerstrand:
>> >> On 06/24/2014 09:25 PM, Jörg Schaible wrote:
>> >>> Alexandre Rostovtsev wrote:
>> >>
>> >>>> On Mon, 2014-06-23 at 22:15 +0200, Jörg Schaible wrote:
>> >>>>> So, why the heck, was the dependency to dev-libs/glib changed
>> >>>>> for an existing ebuild without increasing its version (e.g.
>> >>>>> dbus-glib-0.100.2-r2)?
>> >>>>
>> >>>> Please see
>> >>>> http://article.gmane.org/gmane.linux.gentoo.devel/91615
>> >>
>> >>> These blocks had nothing to do with the multilibs ABI. It has been
>> >>> just the updated versions for the dependencies.
>> >>
>> >>
>> >> For what it is worth, I completely agree significant changes to stable
>> >> ebuilds (hereunder changes to dependencies) should get a revision bump
>> >> and go through normal stabilization procedures.
>> >>
>> >>
>> >
>> > That would be a waste of time and would increase the overall workload
>> > on arch teams who already need 2-4 weeks to keep up with the queue.
>> > There is no reason to re-stabilize a package after a build-time bug has
>> > been fixed by adjusting the version of a dependency.
>> >
>> > Moreover, the fix that was applied was very important.
>>
>>
>> And, since the official tree did not have an older version of those deps
>> anyway, the upgrade in the stable dependent ebuilds was unnecessary. It
>> just broke the tree for users with local or other overlays.
>
> But people could have older versions of those deps installed, and then
> their systems would slowly become broken on upgrades. Since the issues
> wouldn't be caught early properly, they would trigger incorrect
> installs of another packages and a few dep-tree branches further,
> an unexpected hard-to-debug failures.
OK, you have a point. However, it is more dependent on the way people use
emerge. This scenario could not have happen to me, I call emerge always
with:
emerge -uDvta --changed-use --with-bdeps=y
Cheers,
Jörg
next prev parent reply other threads:[~2014-06-26 22:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 20:15 [gentoo-dev] Changes in installed ebuilds Jörg Schaible
2014-06-23 23:14 ` [gentoo-dev] " Duncan
2014-06-24 0:49 ` [gentoo-dev] " Alexandre Rostovtsev
2014-06-24 19:25 ` [gentoo-dev] " Jörg Schaible
2014-06-24 20:47 ` Kristian Fiskerstrand
2014-06-24 21:15 ` hasufell
2014-06-25 22:48 ` [gentoo-dev] " Jörg Schaible
2014-06-26 7:13 ` Michał Górny
2014-06-26 22:04 ` Jörg Schaible [this message]
2014-06-24 21:27 ` [gentoo-dev] " hasufell
2014-06-25 22:46 ` [gentoo-dev] " Jörg Schaible
2014-06-25 10:24 ` [gentoo-dev] " Jan Matejka
2014-06-25 22:42 ` [gentoo-dev] " Jörg Schaible
2014-06-25 23:31 ` Alex Xu
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='loi5d7$n1j$1@ger.gmane.org' \
--to=joerg.schaible@gmx.de \
--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